UCP/RNDV: Use four read paths on ConnectX-9 XDR#11643
Closed
roiedanino wants to merge 1 commit into
Closed
Conversation
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.
Summary
Detect ConnectX-9 XDR interfaces and expose four transport paths for RDMA READ operations.
Rendezvous GET ZCOPY registers both the existing two-path protocol and a four-path protocol, allowing protocol selection to choose by message size. Rendezvous PUT and AM preserve their existing automatic two-path behavior, and explicit lane settings remain authoritative.
Design
Hardware detection uses the ConnectX-9 PCI identifier and XDR link speed rather than the CPU model.
UCX_MAX_RNDV_RAILS=autokeeps a two-device baseline while allowing transports to expose additional read paths on a single device.Supersedes #11625.