mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[PR #695] Fix LL dispatch RC QP assert for all-P2P topologies #712
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#712
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/695
Author: @xiayan0118
Created: 7/22/2026
Status: 🔄 Open
Base:
main← Head:fix/ll-dispatch-rc-qp-p2p-gate📝 Commits (1)
87d8305Fix LL dispatch RC QP assert for all-P2P topologies📊 Changes
1 file changed (+15 additions, -2 deletions)
View changed files
📝
csrc/kernels/legacy/internode_ll.cu(+15 -2)📄 Description
Summary
Low-latency dispatch currently asserts
num_rc_per_pe >= num_local_expertsunconditionally on SM 0. With NVSHMEM 3.6, optional IBGDA may leavenum_rc_per_pe == 0even when every remote rank is directly reachable through P2P. That poisons single-host / all-local jobs (e.g. B200) even though every send/count path already falls back to the P2P pointer whennvshmemi_get_p2p_ptr(...) != 0.Gate the RC QP requirement on per-peer P2P reachability: require RC QPs only if at least one non-self peer has no P2P pointer.
Related reports: #134, #488 (same
num_rc_per_pefamily; this PR specifically covers the LL dispatch all-P2P case).Change
In
csrc/kernels/legacy/internode_ll.cudispatch:nvshmemi_get_p2p_ptr(rdma_recv_count, rank, dst_rank)num_rc_per_pe >= num_local_expertsonly whenneeds_ibgdais trueTest plan
num_rc_per_pe == 0) succeeds when all peers are P2P-reachableMade with Cursor
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.