Skip to content

[dev] [DeepSeek-v4] Context Parallel support#5087

Draft
kunlunl wants to merge 22 commits into
NVIDIA:devfrom
kunlunl:codex/dsv4-cp-fallback
Draft

[dev] [DeepSeek-v4] Context Parallel support#5087
kunlunl wants to merge 22 commits into
NVIDIA:devfrom
kunlunl:codex/dsv4-cp-fallback

Conversation

@kunlunl

@kunlunl kunlunl commented Jun 1, 2026

Copy link
Copy Markdown
Contributor
  • I, the PR author, have personally reviewed every line of this PR.

What does this PR do ?

Add CP support for DS v4

Depends on #5011

⚠️ 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
  • 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.

@copy-pr-bot

copy-pr-bot Bot commented Jun 1, 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.

@hxbai hxbai changed the title dsv4 cp support [dev] [DeepSeek-v4] Context Parallel support Jun 1, 2026
@hxbai hxbai mentioned this pull request Jun 1, 2026
3 tasks
@dingqingy-nv dingqingy-nv added 26.06.01 deepseekv4 DeepSeek V4 PRs labels Jun 9, 2026
hxbai and others added 4 commits June 10, 2026 03:35
…/dsv4-cp-fallback

# Conflicts:
#	megatron/core/transformer/experimental_attention_variant/csa.py
#	megatron/core/transformer/experimental_attention_variant/deepseek_v4_hybrid_attention.py
#	megatron/core/transformer/experimental_attention_variant/dsa.py
#	megatron/core/transformer/experimental_attention_variant/dsa_kernels.py
#	tests/unit_tests/transformer/experimental_attention_variant/test_attention_variant_csa.py
#	tests/unit_tests/transformer/experimental_attention_variant/test_dsa_kernels.py
#	tests/unit_tests/transformer/experimental_attention_variant/test_dsv4_hybrid_native_parity.py
@dingqingy-nv dingqingy-nv removed 26.06.01 deepseekv4 DeepSeek V4 PRs labels Jun 11, 2026
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.

3 participants