Skip max_device_cache_size setter when BAR1 memory isn't present on the GPUs in the system#814
Merged
rapids-bot[bot] merged 4 commits intorapidsai:branch-25.10from Sep 9, 2025
Conversation
kingcrimsontianyu
added
non-breaking
Contributor
|
/ok to test f0e108a |
Contributor
|
Code needs to go through the linter. I'll fix this. |
Contributor
|
/ok to test 91e1913 |
Contributor
|
/ok to test ad60204 |
Contributor
|
Further note: In cuFile shipped with CUDA 13, the call to |
kingcrimsontianyu
approved these changes
Sep 8, 2025
Contributor
|
/merge |
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
3 participants
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've seen multiple issues over the months from DGX Spark users when it comes to this specific file. This PR address these issues by applying a skip for the max_device_cache_size (cuFileDriverSetMaxCacheSize) setter by examining the output of nvidia-smi.