mem: Expose memory bandwidth and latency for SimpleMemory
Review Request #3275 - Created Jan. 13, 2016 and discarded
| Information | |
|---|---|
| Matthew Poremba | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 11310:8ddcef48674b
---------------------------
mem: Expose memory bandwidth and latency for SimpleMemoryExpose SimpleMemory bandwidth and latency parameters to the command line.
This allows for easier simulation of fixed latency memory controllers to
facilitate simple limit-study investigations.
I am not massively thrilled, but our current config system definitely has some challenges. The biggest issue here is that the options only apply to a very specific instance of the memory controller, and I see how users may get confused. If you want to go down this route we should at least check and warn if the values are not used. Also, how does it interact with a multi-channel memory? Lastly, the existing memory command-line options are "mem" and not "memory".
Change Summary:
Added warns when options are used with non-SimpleMemory classes. Move MemConfig lines above elastic trace setup (elastic trace trumps).
Description: |
|
||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+33 -1) |
-
configs/common/MemConfig.py (Diff revision 2) -
elif
-
configs/ruby/Ruby.py (Diff revision 2) -
elif
Description: |
|
||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 3 (+31 -1) |
