Hi Aritra, The CleanEvict packet don’t have data so it cannot do write in the cache. As Nikos said, the main purpose is to update the snoop filter. So when cache see a CleanEvict pkt, it either pass that pkt on to downstream when it misses the cache or stop the pkt if it hits. A side effect is when a cache see a CleanEvict and has the blk in its write queue, it indicates that blk don’t exist in peer caches so the wbpkt can clear the BlockCached bit if it’s original there. You can find this logic in cache/base.cc:1 <http://base.cc:1229/>078~1093 under current release.
Wenqi > On Mar 3, 2021, at 13:37, bagchi95aritra--- via gem5-users > <gem5-users@gem5.org> wrote: > > Hi Nikos, > > Thanks for your response. If possible, could you also indicate what gem5 > cache does when it sees these CleanEvicts? If they are, as you said, write > backs originated for clean (not dirty) cache lines, then the cache shouldn’t > write the data. But then, what does it do? > > Thanks and regards, > Aritra > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
