----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2072/#review5002 -----------------------------------------------------------
How can we get this into shape, and how does it align with: http://reviews.gem5.org/r/1822/? Also, if all we do is add latency, how does it affect the throughput (are we assuming pipelining or not)? - Andreas Hansson On Jan. 9, 2014, 10:06 a.m., Sophiane SENNI wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/2072/ > ----------------------------------------------------------- > > (Updated Jan. 9, 2014, 10:06 a.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > This patch allows specifying different cache latency for read and write > access. (In the code, the hit_latency parameter is actually the read_latency) > > > Diffs > ----- > > src/mem/cache/BaseCache.py 6a043adb1e8d > src/mem/cache/base.hh 6a043adb1e8d > src/mem/cache/base.cc 6a043adb1e8d > src/mem/cache/cache_impl.hh 6a043adb1e8d > src/mem/cache/tags/lru.cc 6a043adb1e8d > > Diff: http://reviews.gem5.org/r/2072/diff/ > > > Testing > ------- > > I used --debug-flags command to check read hit latency and write hit latency > for Dcache and Icache. I checked the time between a request sent by the cpu > and the response sent by the cache memory. > > > Thanks, > > Sophiane SENNI > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
