You'd need to look carefully at what you're actually seeing in the cache. If the cache tries to send a packet multiple times, it might you'll see multiple traces of the same request. You'll also see ReadEx requests go out of the L2.
Ali On Aug 14, 2011, at 5:12 PM, Dawei Wang wrote: > Hello, everyone, > > Today I have simulate one of the PARSEC benchmarks, collecting cache > access activities, the following is the command line > > build/ALPHA_FS/m5.opt --trace-start=2000000000000 > --trace-file=cache.trc --debug-flags=Cache configs/example/fs.py -n 4 > --script=../parsec_lib/scripts/blackscholes_4c_simdev.rcS --detailed > --caches --l2cache -F 5000000000 > > I am interesting in cache coherence protocol, so I count the ReadExReq > from cache.trc and stats.txt file. Below are the results > > $cat cache.trc | grep ReadExReq | wc -l > 280468 > > $cat parsec/blackscholes/stats.txt | grep system.l2.ReadExReq_accesses::total > system.l2.ReadExReq_accesses::total 9175 > # number of ReadExReq accesses(hits+misses) > > system.l2.ReadExReq_accesses::total 5680 > # number of ReadExReq accesses(hits+misses) > > system.l2.ReadExReq_accesses::total 1477 > # number of ReadExReq accesses(hits+misses) > > system.l2.ReadExReq_accesses::total 9527 > # number of ReadExReq accesses(hits+misses) > > Total system.l2.ReadExReq_accesses of the statis.txt is > 9175+5680+1477+9527= 25859, where as the cache.trc is 280468, the > difference is too big ( 1:10.85 ). > > Can anyone give a reasonable explanation? Which one should we trust, > or both are right? > > Thanks in advances > > Dawei > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
