Conversation
Add a pipelined writeback unit for increased bandwidth and limit acquires to avoid tilelink deadlock
Collaborator
|
We should PR this to mainline boom instead to not muddy the water of academic results between what NTNU publishes and what the rest works with. I think this can be useful for everybody else, and since you made configuration switches, the acceptance will be straightforward. |
This file contains hidden or 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
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.
Type of change: new feature
Impact: new rtl
Development Phase: implementation
Release Notes
This PR includes two related additions. One is adding a pipelined writeback unit which improves memory bandwidth for eviction-heavy applications. The second is adding an option for not issuing Tilelink acquires while a Tilelink release is in progress, which avoids a deadlock experienced while devoloping the pipelined writeback unit.