Well, grep does not result in any readLatency ... hitLatency and responseLatency are what you are looking for and they are used for both reads and writes. See src/mem/cache/base.cc.
Thanks, Amin On Thu, Jul 10, 2014 at 8:31 PM, Qi Jia via gem5-users <gem5-users@gem5.org> wrote: > Hi, everyone, > > I am looking at codes in classical cache. I find for Read operation, the > codes consider the readLatency. But for writeback, no latency is > considered, even if it is a write miss, we still allocate a new block > directly and write the new data. Then does it mean every writeback would be > considered as a write hit? > > Please correct me if I am wrong. Any suggestion is appreciated, thanks in > advance. > > -- > Qi Jia > Graduate Student > Department of Electrical and Computer Engineering > North Carolina State University, Raleigh > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
