[TRTLLM-15344][feat] nixl bounce v2 (1/6): foundation components - #17603
Draft
chuangz0 wants to merge 1 commit into
Draft
[TRTLLM-15344][feat] nixl bounce v2 (1/6): foundation components#17603chuangz0 wants to merge 1 commit into
chuangz0 wants to merge 1 commit into
Conversation
1 task
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>
chuangz0
force-pushed
the
bounce-v2/p1-foundations
branch
from
August 13, 2026 05:18
bca0f08 to
43a047a
Compare
Collaborator
Author
|
/bot run --disable-fail-fast |
Collaborator
|
PR_Github #65810 [ run ] triggered by Bot. Commit: |
Collaborator
|
PR_Github #65810 [ run ] completed with state
|
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 1/6 of splitting the NIXL bounce-buffer v2 transport (#15780) into reviewable pieces. This PR adds the dependency-free foundation components under
cpp/tensorrt_llm/executor/cache_transmission/nixl_utils/bounce/:BuddyAllocator— power-of-two buddy allocator used for bounce-buffer creditsBounceArena— shared GPU data arena (alloc / address mapping / shutdown)ExecPool— execution-context pool (stream / event / scratch / host-pinned buffers)GatherScatterKernel— CUDA gather/scatter kernel for staging KV blocksBounceNvtx— NVTX instrumentation helpersNothing is wired into production paths yet; the code is only reachable from its unit tests. The transport core and the
NixlTransferAgentintegration land in later parts.Stack: part 1/6 · umbrella: #15780 (full design & motivation)
Test Coverage
Pre-merge CI wiring is included: this PR adds the
executor_bouncectest group (cpp/test_unit_tests.py::test_unit_tests[executor_bounce-90], H100 pre_merge inl0_h100.yml). ctest discovers tests by directory, so the tiers added by later parts of the stack run automatically without further CI changes; part 6 tightens the group with a built-artifact guard for the NIXL E2E test.cpp/tests/unit_tests/executor/bounce/buddyAllocatorTest.cppcpp/tests/unit_tests/executor/bounce/bounceArenaTest.cpp(GPU)cpp/tests/unit_tests/executor/bounce/execPoolTest.cpp(GPU)cpp/tests/unit_tests/executor/bounce/gatherScatterKernelTest.cpp(GPU)PR 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