[TRTLLM-15344][feat] nixl bounce v2 (2/6): wire protocol and transfer plan - #17604
Draft
chuangz0 wants to merge 2 commits into
Draft
[TRTLLM-15344][feat] nixl bounce v2 (2/6): wire protocol and transfer plan#17604chuangz0 wants to merge 2 commits into
chuangz0 wants to merge 2 commits into
Conversation
This was referenced Aug 13, 2026
Buddy allocator, shared data arena, execution-context pool, and the gather/scatter CUDA kernel, plus their unit tests. These are the dependency-free building blocks of the NIXL bounce-buffer v2 transport; nothing is wired into production paths yet. Signed-off-by: Chuang Zhu <111838961+chuangz0@users.noreply.github.com>
Bounce config (env-var parsing), wire message codec (control-plane messages + capability handshake encode/decode), and the transfer-plan builder that maps a TransferRequest onto bounce chunks. Unit-tested; still not reachable from production paths. Signed-off-by: Chuang Zhu <111838961+chuangz0@users.noreply.github.com>
chuangz0
force-pushed
the
bounce-v2/p2-protocol
branch
from
August 13, 2026 05:18
8724620 to
03b063a
Compare
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.
@coderabbitai summary
Description
Part 2/6 of splitting the NIXL bounce-buffer v2 transport (#15780) into reviewable pieces. This PR adds the protocol layer:
BounceConfig— env-var driven configuration (byte-size suffix parsing, limits, opt-in knobs)BounceMessage— control-plane wire codec (chunk grant/complete messages + the capability handshakeencodeHandshake/decodeHandshakeused during agent connection)BounceTransferPlan— maps aTransferRequestonto bounce chunks (region splitting, size limits)Pure logic, unit-tested, still not reachable from production paths.
Stack: part 2/6, stacked on #17603 — review only the last commit (
nixl bounce v2 (2/6)); the earlier commits belong to part 1. Umbrella: #15780.Test Coverage
cpp/tests/unit_tests/executor/bounce/bounceConfigTest.cppcpp/tests/unit_tests/executor/bounce/bounceMessageCodecTest.cppcpp/tests/unit_tests/executor/bounce/bounceTransferPlanTest.cppPR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.🤖 Generated with Claude Code