[S-TIR][Dlight] Add layered fall back strategy to handle missing attr max_shared_memory_per_block#19453
Merged
Merged
Conversation
… 'max_shared_memory_per_block'
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a robust fallback mechanism for determining the maximum shared memory per block across various GPU targets. It adds the get_max_shared_memory_per_block utility function in common_analysis.py, which provides default values for CUDA, ROCm, Metal, OpenCL, and Vulkan when the target attribute is not explicitly defined. The gemv and low_batch_gemv schedules were updated to utilize this new function. Feedback suggests moving the hardcoded mapping dictionary to a module-level constant to optimize performance and improve code structure.
Contributor
Author
mshr-h
reviewed
Apr 28, 2026
mshr-h
approved these changes
Apr 29, 2026
Contributor
Author
|
Thanks to @mshr-h 😄 |
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.
Hi Committers,
This PR is trying to fix issues #19419. Any suggestions would be appreciated if you are available.
Root Cause
max_shared_memory_per_blockand it would causeKeyErrorSolutions
max_shared_memory_per_block