mem: Remove RubyMemoryControl and rely on DRAMCtrl
Review Request #2725 - Created April 2, 2015 and discarded
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 10790:2db4eeebab53 --------------------------- mem: Remove RubyMemoryControl and rely on DRAMCtrl This patch aims to ease maintenance and avoid confusion when it comes to DRAM modelling in gem5. The DRAMCtrl model is fast, accurate, integrated with power models, and covers a wide range of DRAM variants. Thus, there is really no need to keep the RubyMemoryControl.
I'm for removing this code. However, this patch needs to be pushed first: http://reviews.gem5.org/r/2702/ since in the current state restoring a checkpoint with Ruby is broken.
Instead of abruptly removing the RubyMemoryControl, can we just deprecate it and add a warning that it will eventually be removed (or at a specific time in the future)? In addition to existing gem5-gpu code and my personal patches, I'm aware of at least one other group that has pretty significant code that depends on the RubyMemoryControl. Migrating code to the new controllers is likely to involve some non-trivial dev+debug.
Note: I suspect this code removal request is a bit different from the InOrderCPU removal request, since the RubyMemoryControl is a single component that has been a basis for a few memory controller optimization studies.