Skip to content

Nemo-RL Refit#3520

Open
wdykas wants to merge 44 commits intoNVIDIA:mainfrom
wdykas:nemo-refit
Open

Nemo-RL Refit#3520
wdykas wants to merge 44 commits intoNVIDIA:mainfrom
wdykas:nemo-refit

Conversation

@wdykas
Copy link
Contributor

@wdykas wdykas commented Feb 20, 2026

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 the @mcore-oncall.

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]
Loading

Pre-checks

  • I want this PR in a versioned release and have added the appropriate Milestone (e.g., Core 0.8)
  • 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

The following process is enforced via the CODEOWNERS file for changes into megatron/core. For changes outside of megatron/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

  1. Attach the Expert Review label when your PR is ready for review.
  2. GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.

⚠️ Only proceed to the next step once all reviewers have approved, merge-conflict are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

(Step 3): Final Review

  1. Add Final Review label
  2. GitHub auto-assigns final reviewers based on your changes. They will get notified and pick up your PR soon.

(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, select Cherry-pick to 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.com or zijiey@nvidia.com.

Merging your PR

Any member of core-adlr and core-nemo will be able to merge your PR.

@copy-pr-bot
Copy link

copy-pr-bot bot commented Feb 20, 2026

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.

@wdykas
Copy link
Contributor Author

wdykas commented Feb 23, 2026

/ok to test b99e518

@wdykas wdykas marked this pull request as ready for review February 27, 2026 21:52
@wdykas wdykas requested review from a team as code owners February 27, 2026 21:52
@svcnvidia-nemo-ci svcnvidia-nemo-ci requested a review from a team February 27, 2026 21:52
@wdykas
Copy link
Contributor Author

wdykas commented Feb 27, 2026

/ok to test cdf70c4

@wdykas
Copy link
Contributor Author

wdykas commented Feb 27, 2026

/ok to test fccbff6

@wdykas
Copy link
Contributor Author

wdykas commented Feb 27, 2026

@sidsingh-nvidia @santhnm2 @kvareddy Here is what we have been using with NeMo. We will need more changes for FP8 format change but I figure that come later as we need to keep updated megatron-LM

// Required so that NVSHMEM put() on another CUDA stream can read correct
// pack data from the send buffer. Without this, writes may remain in L2
// cache, invisible to the NIC's DMA engine.
__threadfence_system();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a test case that hit the race condition and produced incorrect output? If so can we add this to the test suite?

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.

6 participants