Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3D dram config parameters #2

Open
joaopaulocl opened this issue Jul 17, 2017 · 6 comments
Open

3D dram config parameters #2

joaopaulocl opened this issue Jul 17, 2017 · 6 comments

Comments

@joaopaulocl
Copy link

Hi,
I trying to use the 3D dram config file, but I getting some errors.
At first, I ran as it is in the repository and it outputs a float pointing exception. I found the source of exception by debugging it and I included the following parameters (mem_data_width = 8 and num_clk = 2) as a workaround.
Then, I ran it again and found some weird values for timing (tRCD, tRAS, tCAS), power and TSV components. Some of them presents values up to e+107 ns and e+54 nJ. When I run with stacked-die-count equals to 1, I get some reasonable values for timing and energy.
Has anyone came across this problem?
I am also interested in the parameters used in the cacti-3DD paper.
Thanks in advance.

@ghost
Copy link

ghost commented Nov 29, 2017

Hi,
Even I am facing these issues
@joaopaulocl were you able to fix these issue?

Thanks.

@joaopaulocl
Copy link
Author

@splurgein Unfortunately no.

@ghost
Copy link

ghost commented Nov 29, 2017

@joaopaulocl thanks for the quick reply. It's quite strange that a lot of people are making use of cacti for modeling 3D memory and no one has yet posted a fix for this issue.

@iamcksong
Copy link

@splurgein and @joaopaulocl
There is a code bug in the file of parameter.cc.
The line of "tsv_length *= g_ip->num_die_3d;" should be moved to line 846, which is only multiplied once when the line includes an option of -tsv_length.

@joaopaulocl
Copy link
Author

joaopaulocl commented Apr 23, 2018

Thanks @iamcksong, it worked for me. Are you planning to pull this amendment?

@nicmcd
Copy link
Member

nicmcd commented Jun 26, 2018

Please submit a pull request for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants