Update AlltoAll and AlltoAllv API for 2.28.3 compatibility #161
+6
−0
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
Signed-off-by: ravaidya <[email protected]>
rahulvaidya20
requested review from
AbandiGa,
AtlantaPepsi,
BertanDogancay,
JhaShweta1,
Kapil-Shyam-Pawar,
KawtharShafie,
Nikhil-Nunna,
PJAvinash,
PedramAlizadeh,
alex-breslow-amd,
amd-mengshwu,
atulkulk,
corey-derochie-amd,
ddebonis-amd,
gilbertlee-amd,
haripriyaayyalasomayajula,
isaki001,
mberenjk,
mustafabar,
nawrinsu,
nileshnegi,
nusislam,
speriaswamy-amd,
thananon,
weilewei and
wenkaidu
as code owners
wenkaidu
approved these changes
Dec 10, 2025
nusislam
approved these changes
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Details
Do not mention proprietary info or link to internal work items in this PR.
Work item: Internal
What were the changes?
Update AlltoAll and AlltoAllv API calls to maintain compatibility with RCCL 2.28.3.
Why were the changes made?
To ensure compatibility with RCCL versions greater than 2.28.3.
How was the outcome achieved?
By updating the API calls appropriately using the RCCL version check.
Additional Documentation:
What else should the reviewer know?