UCT/IB/MLX5/GDAKI: Try VMM allocation. - #11795
Open
rakhmets wants to merge 1 commit into
Open
Conversation
rakhmets
force-pushed
the
topic/rc-gda-alloc-vmm
branch
from
August 19, 2026 14:26
5549a4c to
5d499f0
Compare
rakhmets
force-pushed
the
topic/rc-gda-alloc-vmm
branch
from
August 19, 2026 14:30
5d499f0 to
4a5f958
Compare
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.
What?
GDAKI now tries CUDA VMM fabric allocation and falls back to
cuMemAllocif it is not available.For VMM memory, DMA sync is set with
CU_CTX_SYNC_MEMOPSon the GDAKI CUDA context.Why?
GDAKI previously always allocated with
cuMemAlloc. VMM fabric allocations are created RDMA capability.UCS_TRYkeeps the oldcuMemAllocpath on systems where CUDA VMM fabric allocation is not available.