nvidia-peer-memory: prefer in-tree nvidia_peermem over legacy nv_peer_mem - #1390
Open
100-JM wants to merge 1 commit into
Open
nvidia-peer-memory: prefer in-tree nvidia_peermem over legacy nv_peer_mem#1390100-JM wants to merge 1 commit into
100-JM wants to merge 1 commit into
Conversation
…_mem Driver R470.42.01 and later ship nvidia_peermem as part of the driver; the out-of-tree nv_peer_mem DKMS module does not exist there. The role unconditionally ran dkms autoinstall + modprobe nv_peer_mem on DGX systems and failed on current DGX OS. Probe for the in-tree module with modinfo and load it when present; fall back to the legacy nv_peer_mem path only when it is absent. Observed on DGX OS 7.5.0 / driver 580.126.20: modprobe: FATAL: Module nv_peer_mem not found in directory /lib/modules/6.8.0-106-generic Signed-off-by: 백지명 <wlaud9805@gmail.com>
100-JM
marked this pull request as ready for review
September 3, 2026 13:39
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.
Problem
roles/nvidia-peer-memoryassumes the out-of-treenv_peer_memDKMS module on DGX systems. Since driver R470.42.01 the equivalentnvidia_peermemmodule ships in-tree with the driver andnv_peer_memis not available, so the role fails on current DGX OS:There is no variable to disable the role from
slurm-cluster.yml; only thenvidia-peer-memorytag.Reproduced on DGX OS 7.5.0, driver 580.126.20.
Fix
Probe for
nvidia_peermemwithmodinfo. When present, load it and skip the legacy DKMS/nv_peer_mem/service path. When absent, behaviour is unchanged.Verification
Failure reproduced on DGX OS 7.5.0 / driver 580.126.20. On the same system
lsmodshows the in-tree module already loaded (nvidia_peermem 16384 0, used byib_uverbs), so the new probe takes the in-tree branch and the legacy DKMS/nv_peer_mem path is skipped.