L1 TLB: Add support for configurable L1 TLB (sets/ways) #2574
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
ingallsj
approved these changes
Aug 26, 2020
ingallsj
requested changes
Aug 26, 2020
There was a problem hiding this comment.
I like it!
I am not sure if I should rename nTLBEntries to nTLBWays which is more relevant with this approach.
I'm in favor of renaming nTLBEntries to nTLBWays, as used in this PR, else calculating nTLBWays as nTLBEntries/nTLBSets.
Also, can you please rebase this PR onto a newer version of the main branch to resolve merge conflicts?
ncppd
force-pushed
the
configurable-L1-TLB-v1
branch
from
bdda9e2 to
5483823
Compare
ingallsj
approved these changes
Aug 27, 2020
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.
With this PR I add support for configurable L1 Data/Instruction TLB by specifying the number of the sets and entries. The sectored TLB entry mechanism is supported along with the configurable TLB logic. I also add replacement policy support for the set-associative TLB mechanism using the existing replacement policies.
(I am not sure if I should rename nTLBEntries to nTLBWays which is more relevant with this approach.)
Type of change: other enhancement
Impact: no API modification
Development Phase: implementation