----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2934/#review6657 -----------------------------------------------------------
I am surprised we need this class. If one cube is using all links connected to the same host, then we can simply use the address interleaving support in the crossbar to interleave between the serial links. We can do this on any granularity we want, e.g. 64 bytes. If different hosts are talking to the cube, then we do not need an interleaving at all on the host side. - Andreas Hansson On July 1, 2015, 10:31 a.m., Erfan Azarkhish wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/2934/ > ----------------------------------------------------------- > > (Updated July 1, 2015, 10:31 a.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > The class HMCController inherits from NoncoherentXBar with two simple > modifications: > 1. It forwards the receiving requests on its slave port to the master ports > using a round- > robin fashion > 2. It accepts overlapping address ranges on its master ports ([3]). > This patch and the subsequent chain of patches aim to model a simple Hybrid > Memory Cube device in gem5 > Please apply the complete chain before running the simulation. > > > Diffs > ----- > > src/mem/HMCController.py PRE-CREATION > src/mem/hmc_controller.hh PRE-CREATION > src/mem/hmc_controller.cc PRE-CREATION > > Diff: http://reviews.gem5.org/r/2934/diff/ > > > Testing > ------- > > > Thanks, > > Erfan Azarkhish > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
