[7.0] Check for hipblaslt workspace size during tuning (#4182) #4191
Conversation
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
We used default workspace size of 256 MB during tuning, however, it turns out that some of the solutions require a workspace size larger than 256MB. This causes memory access failures. To fix this, we skip over solutions that require more than 128MB of workspace size. The reason for choosing 128MB is for efficient memory usage.
ahsan-ca
approved these changes
Jul 31, 2025
causten
changed the title
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.
We used default workspace size of 256 MB during tuning, however, it turns out that some of the solutions require a workspace size larger than 256MB. This causes memory access failures.
To fix this, we skip over solutions that require more than 128MB of workspace size. The reason for choosing 128MB is for efficient memory usage.