[v2.4.x] prov/efa: use dmabuf for CUDA MR registration#12216
Open
sara4dev wants to merge 1 commit intoofiwg:v2.4.xfrom
Open
[v2.4.x] prov/efa: use dmabuf for CUDA MR registration#12216sara4dev wants to merge 1 commit intoofiwg:v2.4.xfrom
sara4dev wants to merge 1 commit intoofiwg:v2.4.xfrom
Conversation
Contributor
|
Can you please sign your commit? |
a-szegel
reviewed
May 5, 2026
Contributor
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.
Summary
ofi_hmem_get_dmabuf_fd()andibv_reg_dmabuf_mr()flow forFI_HMEM_CUDARoot Cause
CUDA HMEM registrations without
FI_MR_DMABUFwere not included in the EFA provider's dmabuf path, unlike Neuron and ROCr. That made CUDA memory fall through to plainibv_reg_mr()with a GPU virtual address, which can fail withEFAULT.References #12019.
Validation
Tested in a GB200 cluster