-
Notifications
You must be signed in to change notification settings - Fork 99
Add NUMA node ID attribute for NUMA aware allocation between CPU, GPU and NICs #690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
shivamerla
wants to merge
1
commit into
NVIDIA:main
Choose a base branch
from
shivamerla:add_numa_node_attribute
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting! Would this be entirely exceptional, or is this an expected scenario on some systems?
This leads me to thinking:
On non-NUMA systems this should probably not be a warning. On those systems, I suppose this code path is expected, and maybe it's worth emitting an info-level log message.
On NUMA systems this should maybe be an error. At least I'd like to hear our thoughts about this.
How can we reliably distinguish a NUMA from a non-NUMA system (as a reference point)?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ref docs for
nvmlDeviceGetNumaNodeId()indicate that we should distinguish three types of errors:I don't want to answer my own questions from above, but it looks like we probably want to give
NVML_ERROR_NOT_SUPPORTEDits own code path (not emitting a warning/error log), and thenNVML_ERROR_INVALID_ARGUMENTis handled separately (and maybe that one should be fatal?).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jgehrcke good point, the not supported error can be logged as info instead of warning. After discussing with Kevin, we actually want to use the nvmlDeviceGetMemoryAffinity() . This will give the bitmask of NUMA nodes as the GPU can belong to multiple within the given socket. This means the current
matchAttibuteis not sufficient for this. Instead i will propose a new parameter to allow attributes to be matched from a list instead of a single element.In that case it will be new set of error codes that we need to handle and i will update based on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack, thanks!