Searched hist:11602 (Results 1 - 1 of 1) sorted by relevance
| /gem5/src/mem/cache/ | ||
| H A D | cache.cc | diff 11602:7e0199f80816 Fri Aug 12 09:11:00 EDT 2016 Andreas Hansson <andreas.hansson@arm.com> mem: Update mostly exclusive policy even further This patch takes yet another step in maintaining the clusivity, in that it allows a mostly-inclusive cache to hold on to blocks even when responding to a ReadExReq or UpgradeReq. Previously the cache simply invalidated these blocks, but there is no strict need to do so. The most important part of this patch is that we simply mark the block clean when satisfying the upstream request where the cache is allowed to keep the block. The only tricky part of the patch is in the memory management of deferred snoops, where we need to distinguish the cases where only the packet was copied (we expected to respond), and the cases where we created an entirely new packet and request (we kept it only to replay later). The code in satisfyRequest is definitely ready for some refactoring after this. Change-Id: I201ddc7b2582eaa46fb8cff0c7ad09e02d64b0fc Reviewed-by: Nikos Nikoleris <nikos.nikoleris@arm.com> Reviewed-by: Tony Gutierrez <anthony.gutierrez@amd.com> |
Completed in 29 milliseconds