Hi Aritra, When a cache access misses, the cache in turns issues a request to next level cache or memory to request the line. Depending on whether the line needs to be read or written and other heuristics and policies, the cache will require from the line it gets back to have certain attributes. Uniqueness (exclusivity) and cleanness (equality with memory content) are the most commonly used attributes.
In the case of ReadCleanReq, the missing line is requested to be clean, that is up to date with memory. The line will thus be received as one of shared clean or unique clean. A clean line is typically required when a cache knows it is likely to evict it unmodified (i.e., still in clean state). In gem5, this is assumed when a cache is read-only or (mostly) exclusive. Best, Gabriel _______________________________________________ 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
