mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[PR #642] [MERGED] Add fence.proxy.async.shared::cta between mbarrier wait and TMA load. #683
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepEP#683
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/DeepEP/pull/642
Author: @RayWang96
Created: 5/24/2026
Status: ✅ Merged
Merged: 5/26/2026
Merged by: @sphish
Base:
main← Head:fix_fence📝 Commits (2)
1185547Add fence.proxy.async.shared::cta between mbarrier wait and TMA load.0cf14f2Move fence before "mbarrier_arrive"📊 Changes
2 files changed (+10 additions, -1 deletions)
View changed files
📝
csrc/kernels/legacy/internode_ll.cu(+1 -1)📝
csrc/kernels/legacy/utils.cuh(+9 -0)📄 Description
This fixes the issue mentioned in https://github.com/deepseek-ai/DeepEP/issues/621. Compared with the fix in https://github.com/deepseek-ai/DeepEP/pull/632, this version uses a CTA-scope fence, which resolves the problem while preserving performance.
The data race here comes from LDS and TMA loads, so we only need fence.proxy.async.shared::cta; to prevent the TMA load from being issued before LDS has completed.
Thanks to elvircrn's script, I've tried my fix on NVL72, the result is correct and the performance is as good as the original implementation.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.