On Mon, 13 Oct 2014, Andreas Hansson via gem5-dev wrote:
Hi Nilay, Thanks for the clarification. I believe the RubyMemoryController is completely Pareto dominated by the vanilla DRAMCtrl module, but if there is any specific feature/setting missing I would be keen to know. If possible I would like to make sure we use the same controller as a default for all timing simulations (even if the other one would be maintained as a fallback). We could always make RubyMemoryControl a subclass of DRAMCtrl if Brad really wants it to remain in the code base.
I am ready to yield on this. We will switch all the regression tests and config scripts to make use of DRAMCtrl. As of now, I am thinking of letting RubyMemoryController inherit from AbstractMemory, just like SimpleMemory and DRAMCtrl.
_______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
