[Dev] Move some processing into a function so can be compiled - #3220
Merged
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
6 tasks
janEbert
approved these changes
Feb 24, 2026
yaox12
approved these changes
Feb 25, 2026
Contributor
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/22704504035 |
yuzhongw-nvidia
added a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Mar 24, 2026
…NVIDIA#3040, NVIDIA#3220) - Add context parallel (CP) support to GatedDeltaNet via all-to-all communication (tensor_a2a_cp2hp / tensor_a2a_hp2cp) - Refine GDN implementation: replace causal_conv1d_fn with fla.modules.convolution, extract _prepare_qkv_for_gated_delta_rule and _compute_g_and_beta as @jit_fuser methods - Update TransformerConfig to remove CP==1 assertion for gated_delta_net and add linear_attention_type deprecation alias - Enable CP test cases in test_gated_delta_net.py and refactor correctness test to use shared _test_parallel_attention_correctness helper Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Mar 24, 2026
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Mar 24, 2026
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Mar 24, 2026
6 tasks
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Apr 7, 2026
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Apr 10, 2026
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Apr 13, 2026
yuzhongw-nvidia
pushed a commit
to yuzhongw-nvidia/Megatron-LM
that referenced
this pull request
Apr 13, 2026
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.
What does this PR do ?
Use triton to compile some ops for acceleration. PR3559 for main branch.
Contribution process
flowchart LR A[Pre-checks] --> B[PR Tests] subgraph Code Review/Approval C1[Expert Review] --> C2[Final Review] end B --> C1 C2 --> D[Merge]Pre-checks
Core 0.8)Code review
The following process is enforced via the CODEOWNERS file for changes into
megatron/core. For changes outside ofmegatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.For MRs into `main` branch
Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!
(Step 1): Add PR label
Expert Review(Step 2): Collect the expert reviewers reviews
Expert Reviewlabel when your PR is ready for review.Final Review might get declined if these requirements are not fulfilled.
(Step 3): Final Review
Final Reviewlabel(Optional Step 4): Cherry-pick into release branch
If this PR also needs to be merged into
core_r*release branches, after this PR has been merged, selectCherry-pickto open a new PR into the release branch.For MRs into `dev` branch
The proposed review process for `dev` branch is under active discussion.MRs are mergable after one approval by either
eharper@nvidia.comorzijiey@nvidia.com.Merging your PR
Any member of core-adlr and
core-nemowill be able to merge your PR.