configs: model the GPU scalar cache separately from the SQC - #3
Open
Basemism wants to merge 1 commit into
Open
Conversation
Create a distinct scalar-cache object and controller instead of reusing the SQC cache configuration for scalar memory requests. Add independent size and associativity options while continuing to share the SQC Ruby machine type and controller-version namespace required by GPU_VIPER. Keep existing defaults and route scalar sequencers through the new cache without enabling vector-data requests.
There was a problem hiding this comment.
🟢 Approval recommended
The changes are localized to configuration code and appear consistent with the stated goal while preserving defaults, with only minor maintainability feedback.
Pull request overview
This PR updates the GPU_VIPER Ruby configuration to model GPU scalar memory requests with a dedicated scalar L1 cache/controller instead of reusing the existing SQC cache configuration, while preserving existing default behavior.
Changes:
- Adds
ScalarCacheandScalarCntrlto provide a distinct cache object/controller for scalar requests. - Introduces
--scalar-sizeand--scalar-assocCLI options to tune the scalar cache independently. - Routes scalar sequencers through the new scalar cache/controller while keeping scalar requests on the existing SQC machine type/versioning namespace.
File summaries
| File | Description |
|---|---|
| configs/ruby/GPU_VIPER.py | Introduces dedicated scalar cache/controller classes, adds scalar cache sizing options, and switches scalar controller construction to use the new controller. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+278
to
+289
| class ScalarCache(RubyCache): | ||
| dataArrayBanks = 8 | ||
| tagArrayBanks = 8 | ||
| dataAccessLatency = 1 | ||
| tagAccessLatency = 1 | ||
|
|
||
| def create(self, options): | ||
| self.size = MemorySize(options.scalar_size) | ||
| self.assoc = options.scalar_assoc | ||
| if hasattr(options, "sqc_rp"): | ||
| self.replacement_policy = ObjectList.rp_list.get(options.sqc_rp)() | ||
|
|
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.
Create a distinct scalar-cache object and controller instead of reusing the SQC cache configuration for scalar memory requests.
Add size and associativity options while continuing to share the SQC Ruby machine type and controller-version namespace.
Keep existing defaults and route scalar sequencers through the new cache without enabling vector-data requests.