nixl is beta in trtllm

[laikhtewari]

Overview:

Update NIXL integ doc to reflect beta status. Experimental is not well defined feature status

Details:

Doc change

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Documentation
  • Updated NIXL KV cache transfer docs: status moved from Experimental to Beta with revised wording and expectations.
  • Added architecture guidance: NIXL supported on AMD64; ARM64 requires UCX.
  • Clarified stability notes (“may have sharp edges”) while keeping enablement steps unchanged.
  • Confirmed no changes to existing operational guidance for ETCD/NATS; content remains intact.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

👋 Hi laikhtewari! Thank you for contributing to ai-dynamo/dynamo.

Just a reminder: The NVIDIA Test Github Validation CI runs an essential subset of the testing framework to quickly catch errors.Your PR reviewers may elect to test the changes comprehensively before approving your changes.

🚀

[coderabbitai]

Walkthrough

Renamed the NIXL section from Experimental to Beta and adjusted wording accordingly. Added architecture notes: NIXL supported on AMD64; ARM64 requires UCX. Preserved existing enablement steps and ETCD/NATS note. No code or API changes; documentation-only updates to components/backends/trtllm/kv-cache-transfer.md.

Changes

Cohort / File(s)	Summary
Docs: NIXL status and architecture notes components/backends/trtllm/kv-cache-transfer.md	Updated headings and wording from “Experimental” to “Beta” for NIXL KV cache transfer; added AMD64 support note and ARM64 UCX requirement; retained procedural steps and existing ETCD/NATS note; minor formatting adjustments.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I twitch my whiskers, Beta’s here—hooray!
From “Experimental” we hop a surer way.
AMD64? I thump with glee.
ARM needs UCX—carrots don’t come free.
Steps unchanged, my paws still know—
Cache sails smooth where NIXL breezes blow.

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly captures the primary change of updating NIXL to beta status within TRTLLM, directly reflecting the documentation update and remaining concise and focused on the main change.
Description Check	✅ Passed	The description follows the repository’s template by including the Overview, Details, Where should the reviewer start, and Related Issues sections, making it largely complete, though the Reviewers Start section is left blank and the Details section is very brief.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b16b6bc and ae9420e.

📒 Files selected for processing (1)

• components/backends/trtllm/kv-cache-transfer.md (2 hunks)

🧰 Additional context used

🪛 GitHub Actions: Pre Merge Validation of (ai-dynamo/dynamo/refs/pull/3371/merge) by laikhtewari.

components/backends/trtllm/kv-cache-transfer.md

[error] 1-1: Trailing whitespace detected and fixed by pre-commit hook.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build and Test - dynamo

🔇 Additional comments (1)

components/backends/trtllm/kv-cache-transfer.md (1)

27-35: Clear beta positioning and architecture note look good.

Thanks for clarifying the beta status and x86/ARM split; the docs now set expectations accurately while keeping the enablement steps intact.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}