D$: support specifying the cache index when aliasing possible #2697
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
aswaterman
force-pushed
the
dcache-explicit-idx
branch
from
703c0a1
to
528cc73
Compare
Since the same physical address can legally live in multiple places for caches that support aliasing, we can expose this additional degree of freedom. It is useful for decoupled accelerators whose memory addresses have been converted up front. If they use the physical address directly, then they'll often access the wrong set, causing an aliasing miss. If they happen to know which alias is most likely, they can use this new mechanism to choose it. No change for the non-aliasing case.
aswaterman
force-pushed
the
dcache-explicit-idx
branch
from
528cc73
to
1b9b97b
Compare
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.
Since the same physical address can legally live in multiple places for
caches that support aliasing, we can expose this additional degree of
freedom. It is useful for decoupled accelerators whose memory addresses
have been converted up front. If they use the physical address directly,
then they'll often access the wrong set, causing an aliasing miss. If
they happen to know which alias is most likely, they can use this new
mechanism to choose it.
No change for the non-aliasing case.
Related issue:
Type of change: other enhancement
Impact: API addition (no impact on existing code)
Development Phase: implementation
Release Notes