Skip to content

[II] Pack DCP attention LSE as FP32 - #339

Closed
voipmonitor wants to merge 1 commit into
dev/infernal-invocationfrom
agent/ii-dcp-fp32-lse-pack
Closed

voipmonitor wants to merge 1 commit into
dev/infernal-invocationfrom
agent/ii-dcp-fp32-lse-pack

Conversation

@voipmonitor

Copy link
Copy Markdown

Status

Qualified.

Behavior

The DCP all-to-all path converts FP16 or BF16 log-sum-exp tensors to FP32 before packing. The transport preserves each FP32 LSE bit pattern in one FP32 lane or two 16-bit output-dtype lanes, and unpacking returns the global LSE in FP32.

Technical reason

MLA backends may emit LSE in the activation dtype, while the packed DCP protocol interprets the payload as FP32 bits. Normalizing before the Triton pack kernel gives every backend the same wire representation and prevents dtype-dependent bit reinterpretation.

Compatibility

The communication topology, output activation dtype, LSE-weighted combination formula, B12X dispatch, and NCCL fallback are unchanged. FP32 LSE inputs avoid an allocation and retain their existing representation.

Validation

  • Ruff formatting and checks pass.
  • git diff --check passes.
  • 13 pack/unpack tests pass across FP16, BF16, and FP32 output buffers.
  • Four 4-GPU NCCL tests pass for FP16, BF16, and FP32 outputs, including the vLLM workspace-manager path.
  • Distributed tests use a 1 GiB Docker shared-memory allocation required by NCCL 2.31.2.

Normalize activation-dtype LSE tensors to FP32 before the DCP all-to-all pack kernel and preserve their FP32 bit pattern in the output-dtype transport lanes. The unpacked global LSE remains FP32.

The communication topology, output activation dtype, and weighted-combination formula are unchanged.

Validation: Ruff format/check and git diff --check pass. Thirteen pack/unpack tests pass across FP16, BF16, and FP32 output buffers. Four 4-GPU NCCL tests pass with and without the vLLM workspace manager.
@coderabbitai

coderabbitai Bot commented Aug 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@voipmonitor, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d2b70cc8-d6fa-4b70-a900-dd4ef5c2bb29

📥 Commits

Reviewing files that changed from the base of the PR and between ad848fc and 148cd2e.

📒 Files selected for processing (2)
  • tests/distributed/test_dcp_a2a.py
  • vllm/v1/attention/ops/dcp_alltoall.py

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

Comment @coderabbitai help to get the list of available commands.

@voipmonitor

Copy link
Copy Markdown
Author

The behavior implemented by this pull request is preserved unchanged in vLLM #384 as commit be440c0f88fa. Stable Git patch IDs match. Review and merge #384; this pull request is closed to avoid duplicate review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant