Split CACHE.SNOOP.REMOTE_REQ_LOCAL_HITM event per cache level #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dmitriy Ryabtsev <d.ryabtsev@yadro.com>
Closed
bcstrongx
reviewed
Oct 16, 2024
| @@ -36,8 +36,10 @@ | |||
| |CACHE.L2.PREF.MERGE |L2 cache hits caused by prefetcher where data is not yet in cache but was already requested by preceding miss. | |||
| |CACHE.L2.PREF.UNUSED |Number of cachelines brought into L2 by prefetcher and evicted without being accessed even once. | |||
| |CACHE.L2.WB |Writebacks to next level cache or memory. | |||
| |CACHE.SNOOP.LOCAL_REQ_REMOTE_HITM.SPEC |Private cache misses where data was found in another core cache in modified state. This event can be used to accout for contested accesses cases where several cores read/write the same cachelines. | |||
| |CACHE.SNOOP.REMOTE_REQ_LOCAL_HITM |Snoop requests which found cacheline in the core cache in modified state. This event can be used to accout for contested accesses cases where several cores read/write the same cachelines. | |||
| |CACHE.SNOOP.LOCAL_REQ_REMOTE_HITM.SPEC |Private cache misses where data was found in another core cache in modified state. This event can be used to account for contested accesses cases where several cores read/write the same cachelines. | |||
There was a problem hiding this comment.
One thing to keep in mind with this event is that it may only reflect HITMs in a subset of caches. E.g., if the L3/LLC is external, this may only count HITMs in the L1D and L2. I guess the implication is that LOCAL is only guaranteed to cover caches local to (within) the hart. I think that's okay, the kind of sharing cases we're looking for are likely to be getting HITMs in the L1D's of the conflicting harts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.