mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #691] [Proposal] Adding HybridEP compatibility with newer NVSHMEM versions #401
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#401
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?
Originally created by @youngjeong46 on GitHub (Jul 15, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/691
On the main branch v1.x, there was runtime timeout when NVSHMEM modified the way default qpairs were stored by introducing a QP-specific APIs (starting ~3.5.19). It was discussed in issue #553 , and subsequently PR #564 was merged to allow DeepEP to work with the newer NVSHMEM versions. Can those patches (since moved to legacy in the main branch) also be applied to
hybrid-ep? I have a case to use hybrid ep with a newer NVSHMEM version.@0z5a commented on GitHub (Sep 19, 2026):
I’d be happy to take this.
@youngjeong46
I think the safest scope is to port the compatibility approach from #564 into hybrid-ep, rather than changing the HybridEP communication design.