mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[PR #478] Add barrier before nvshmem_team_split_strided to ensure proper initialization #593
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#593
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/478
Author: @pierDipi
Created: 11/3/2025
Status: 🔄 Open
Base:
main← Head:barrier-low-latency📝 Commits (1)
ce054aeAdd barrier before nvshmem_team_split_strided to ensure proper initialization📊 Changes
1 file changed (+3 additions, -1 deletions)
View changed files
📝
csrc/kernels/runtime.cu(+3 -1)📄 Description
I'm getting
Move
nvshmem_barrier_all()to execute beforenvshmem_team_split_stridedrather than after. This is required because team split is a collective operation that must be called by all PEs in the parent team, and all PEs must reach this call in a synchronized manner.Without the barrier after nvshmemx_init_attr(), ranks may complete initialization at different times, leading to race conditions where some PEs attempt to split teams before others have finished NVSHMEM initialization. This can cause undefined behavior and incorrect team formation.
The barrier after team split was unnecessary per NVSHMEM documentation: teams are immediately usable after creation without intervening synchronization.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.