Skip to content

Load the MLA query RoPE dims contiguously in the forward kernel - #8141

Merged
sraman-rgb merged 6 commits into
NVIDIA:mainfrom
sraman-rgb:sraman/mla-rope-fwd-contiguous-load
Oct 16, 2026
Merged

sraman-rgb merged 6 commits into
NVIDIA:mainfrom
sraman-rgb:sraman/mla-rope-fwd-contiguous-load

Conversation

@sraman-rgb

Copy link
Copy Markdown
Contributor

The in-place query RoPE forward (_mla_rope_fwd_inplace_kernel) read the emb_dim RoPE elements of every head with two stride-2 loads, one for the even and one for the odd elements, and with remove_interleaving it wrote them back with two stride-2 stores. It now loads them with one contiguous load and splits the even and odd elements in registers, and writes the remove_interleaving output with one contiguous store. For DeepSeek-V3's query, [4096, 1, 128, 192] in bf16, the kernel takes 11.3 us instead of 18.7 us on VR200.

With the new load the compiler paired the products into FMAs differently, and its pairing also changed with BLOCK_H. The FMAs are now formed explicitly, with the pairings the two-load kernel compiled to, so the output is bit-identical to before at every BLOCK_H the autotuner can choose and no longer depends on BLOCK_H or num_warps. The exception is fp32 q with bf16 cos/sin and inverse=True, where the previous output itself changed with BLOCK_H; it now equals the previous small-BLOCK_H output.

The query replay test now also covers remove_interleaving=True.

  • I, the PR author, have personally reviewed every line of this PR.

What does this PR do?

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share a design doc with the team. If you're unsure what's the best way to do so, contact @NVIDIA/mcore-oncall.

Issue tracking

For PRs from open-source community contributors:

  • New features: a linked issue is required. Please open a feature request and reference it here before submitting the PR.
  • Small updates (bug fixes, minor improvements): a linked issue is recommended and will accelerate the PR review process.

Linked issue:

Contribution process

Pre-checks

  • I have added relevant unit tests
  • I have added relevant functional tests
  • If this PR adds or changes a GPU kernel (Triton, jit_fuser/torch.compile, CUDA extension, TE or external-library dispatch, or a scatter/index accumulation), I have added or updated its bit-exact determinism test and registered it in tests/unit_tests/determinism/kernels/manifest.py (guide)
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

Feel free to message or comment @NVIDIA/mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!

All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.

Step 1: Mark PR as "Ready for Review"

  1. When your PR is ready, click Ready for Review.
  2. An oncall reviewer is auto-assigned and expert reviewers are notified based on your changes.
    • Some PRs may jump straight to step 2. This is determined by .github/CODEOWNERS.

⚠️ Only mark as ready once merge-conflicts are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

Step 2: Final Review

For PRs that change megatron/core, once all expert reviewers have approved, the Final Review label is applied automatically and final reviewers are assigned.

For PRs outside megatron/core, this step is skipped.

Step 3: Approved

Once all required reviewers have approved, the Approved label is applied automatically.

Merge

Any member of mcore-engineers will be able to merge your PR.

The in-place query RoPE forward (_mla_rope_fwd_inplace_kernel) read the
emb_dim RoPE elements of every head with two stride-2 loads, one for the
even and one for the odd elements, and with remove_interleaving it wrote
them back with two stride-2 stores. It now loads them with one contiguous
load and splits the even and odd elements in registers, and writes the
remove_interleaving output with one contiguous store. For DeepSeek-V3's
query, [4096, 1, 128, 192] in bf16, the kernel takes 11.3 us instead of
18.7 us on VR200.

With the new load the compiler paired the products into FMAs differently,
and its pairing also changed with BLOCK_H. The FMAs are now formed
explicitly, with the pairings the two-load kernel compiled to, so the
output is bit-identical to before at every BLOCK_H the autotuner can
choose and no longer depends on BLOCK_H or num_warps. The exception is
fp32 q with bf16 cos/sin and inverse=True, where the previous output
itself changed with BLOCK_H; it now equals the previous small-BLOCK_H
output.

The query replay test now also covers remove_interleaving=True.

Signed-off-by: Siddhartha Raman S <sraman@nvidia.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sraman-rgb
sraman-rgb requested review from a team as code owners October 12, 2026 14:14
@copy-pr-bot

copy-pr-bot Bot commented Oct 12, 2026

Copy link
Copy Markdown

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.

@svcnvidia-nemo-ci
svcnvidia-nemo-ci marked this pull request as draft October 12, 2026 14:14
@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically converted to draft because all PRs must start as drafts.

When you are ready for review, click Ready for Review to begin the review process. This will:

  1. Add the oncall reviewer (optional reviewer)
  2. Add required review teams based on your changes

See the contribution guide for more details.

@sraman-rgb
sraman-rgb marked this pull request as ready for review October 12, 2026 14:15
@svcnvidia-nemo-ci svcnvidia-nemo-ci added the Final Review PR is in the "final review" stage label Oct 12, 2026
@svcnvidia-nemo-ci svcnvidia-nemo-ci added Approved All necessary approvals have been made and removed Final Review PR is in the "final review" stage labels Oct 14, 2026
@sraman-rgb
sraman-rgb enabled auto-merge October 14, 2026 17:32
@sraman-rgb

Copy link
Copy Markdown
Contributor Author

/ok to test a941f26

@sraman-rgb
sraman-rgb added this pull request to the merge queue Oct 14, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Oct 15, 2026
Resolve the conflict in the fused Triton kernel replay tests, where main
now checks that the MLA query RoPE output is finite and this branch adds
remove_interleaving to the test's label. Both are kept.

Signed-off-by: Siddhartha Raman S <sraman@nvidia.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sraman-rgb

Copy link
Copy Markdown
Contributor Author

/ok to test 69322fb

@sraman-rgb

Copy link
Copy Markdown
Contributor Author

/ok to test cdf2549

@nemo-automation-bot

Copy link
Copy Markdown

🔄 Merge queue validation started!

You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/38966892068

Merged via the queue into NVIDIA:main with commit a4b2bee Oct 16, 2026
110 checks passed
@sraman-rgb
sraman-rgb deleted the sraman/mla-rope-fwd-contiguous-load branch October 16, 2026 23:00

This branch was previously deployed

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

Labels

26.12 Approved All necessary approvals have been made complexity: low mlperf

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants