Repository navigation
[WIP-DNM] UCT/IB/MLX5: Purge outstanding AM bcopy operations - #9
Draft
roiedanino wants to merge 1 commit into
Draft
roiedanino wants to merge 1 commit into
roiedanino wants to merge 1 commit into
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
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?
Add native RC mlx5 outstanding-purge support for
uct_ep_am_bcopy()throughuct_rc_mlx5_op_info_fill_am_bcopy(), with small- and large-payload cases using the existing UCT outstanding-purge fixture.This is a stacked follow-up to openucx/ucx#11857. The base branch keeps the incremental diff limited to AM bcopy.
Why?
Fault-tolerance handling needs the AM ID, flags, and buffered payload for outstanding AM bcopy operations, while safely releasing their transport-owned send buffers.
How?
Recognize the single-data-segment SEND layout and match it to its outstanding bcopy descriptor. Use the existing MTU-based packet-count helper and PSN tracking to select undelivered operations. Keep the payload valid through the purge callback, then release the descriptor before completing subsequent flushes.
Reuse the shared endpoint invalidation, token query, purge, and completion flow. Extend AM field and payload comparisons for bcopy without introducing a separate transport-specific fixture.
No send-path changes, new PSN tracking, AM zcopy, RMA, DM, or flush-operation reporting are included.