Fix verbose NVSHMEM_CUMEM_GRANULARITY warning.#115
Merged
romerojosh merged 1 commit intomainfrom Mar 17, 2026
Merged
Conversation
Signed-off-by: Josh Romero <joshr@nvidia.com>
Collaborator
Author
|
/build |
|
🚀 Build workflow triggered! View run |
|
✅ Build workflow passed! View run |
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
1 participant
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.
#113 introduced a workaround for an NVSHMEM issue which forces a setting of
NVSHMEM_CUMEM_GRANULARITYwhen needed. The code prints out a verbose warning if the user hasNVSHMEM_CUMEM_GRANULARITYset in their environment to inform them of the override. This warning can sometimes print in cases where cuDecomp itself set the env var (e.g., on a prior NVSHMEM initialization during autotuning), which is not intended. This PR fixes this extra verbose printing issue.