mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
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#669
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/623
Author: @ko3n1g
Created: 5/6/2026
Status: ❌ Closed
Base:
hybrid-ep← Head:ko3n1g/fix/nvshmem-3.5-runtime-fixes-on-hybrid-ep📝 Commits (6)
379eef7Nvshmem 3 5 runtime fixes (#564)4e38d1dGuard NVSHMEM IBGDA header from host compilation to avoid duplicate symbol1e0dc0ddiag: probe IBGDA device-state contents on rank 0 in notify_dispatch16c4c99probe: drop num_qps_per_rank default 24 → 8 (match notify_dispatch num_channels)6e9cb53probe: force v2 RC indexing (NVSHMEM 3.6.5 uses post-3.5.21 layout despite v1 typedef)cb55a2crevert: force-v2 RC indexing (state IS populated, layout not the cause)📊 Changes
4 files changed (+46 additions, -5 deletions)
View changed files
📝
csrc/kernels/configs.cuh(+15 -0)📝
csrc/kernels/ibgda_device.cuh(+19 -4)📝
csrc/kernels/internode.cu(+11 -0)📝
deep_ep/buffer.py(+1 -1)📄 Description
When DeepEP is against a source build of NVSHMEM starting with NVSHMEM 3.3.20, multiple instances of nvshmemi_ibgda_device_state_d are detected. One from NVSHMEM, another from the kernels.
The locations of QPs within the device state struct changed with the addition of QP-specific APIs.
This change updates DeepEP to work with the new layout.
The ibgda_get_rc function is also templated so that main remains backwards compatible with previous versions of NVSHMEM.
Tested with both internode and low_latency kernels on 4 H100 nodes.
(cherry picked from commit
29d31c0957)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.