----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2993/#review7173 -----------------------------------------------------------
Hi Erfan, I was thinking of something much simpler for the bandwidth throttling, much like what the SimpleMemory is doing, but here we would do it for the "popping" from the send queue. Thus, the incoming packets would still just look at the queues being full or not. We would simply throttle the send events based on the lane bandwidth (you can use Param.MemoryBandwdith for that), and the size of each flit/packet. There should be no need for any rounding or epochs. Simply do not schedule the next send event straight away, but wait enough ticks to make up for the message we just sent. Does that make sense? - Andreas Hansson On Sept. 14, 2015, 1:17 p.m., Erfan Azarkhish wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/2993/ > ----------------------------------------------------------- > > (Updated Sept. 14, 2015, 1:17 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 11096:5ded5036f584 > --------------------------- > Serial Link model for the HMC > > > Diffs > ----- > > src/mem/SConscript 1a9ecb4fe05e > src/mem/SerialLink.py PRE-CREATION > src/mem/serial_link.hh PRE-CREATION > src/mem/serial_link.cc PRE-CREATION > > Diff: http://reviews.gem5.org/r/2993/diff/ > > > Testing > ------- > > > Thanks, > > Erfan Azarkhish > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
