Skip to content

UCT/IB: Use device supported MR flags for dmabuf probing - #12032

Merged
tvegas1 merged 1 commit into
openucx:masterfrom
tvegas1:ib_dmabuf_probe_flags
Oct 6, 2026
Merged

tvegas1 merged 1 commit into
openucx:masterfrom
tvegas1:ib_dmabuf_probe_flags

Conversation

@tvegas1

@tvegas1 tvegas1 commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Why

#11826 fixes EFA falsely disabling dmabuf support due to unsupported MR flags.

What

Apply the one-line functional change from #11826.

How

Pass md->dev.mr_access_flags to ibv_reg_dmabuf_mr().

@svc-nvidia-pr-review

Copy link
Copy Markdown

🤖 Starting review — findings will be posted here when done.

@tvegas1
tvegas1 enabled auto-merge (squash) October 6, 2026 10:16
@svc-nvidia-pr-review

Copy link
Copy Markdown

Residual coverage gap worth being aware of: the only behavior change is on EFA hardware, and contrib/ibmock's ibv_reg_dmabuf_mr() stub (stubs.c:163) unconditionally returns NULL, so CI/gtest cannot exercise the corrected detection path. The fix therefore relies on manual verification on an EFA device; if the author has such a run, it would be good to reference it in the PR description.

@tvegas1
tvegas1 merged commit deaa328 into openucx:master Oct 6, 2026
162 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants