mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[PR #761] [CLOSED] docs: document mlx5 requirement for legacy IBGDA #763
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#763
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/761
Author: @dvd233
Created: 9/22/2026
Status: ❌ Closed
Base:
main← Head:fix/docs-mlx5-ibgda-759📝 Commits (1)
6188bb4docs: document mlx5 requirement for legacy IBGDA📊 Changes
1 file changed (+17 additions, -0 deletions)
View changed files
📝
docs/nvshmem.md(+17 -0)📄 Description
Summary
Clarify the RDMA adapter prerequisites for DeepEP V1's NVSHMEM-backed internode and low-latency paths.
Why
DeepEP V1 enables
NVSHMEM_IB_ENABLE_IBGDA=1for these paths. Issue #759 reports that on Alibaba Cloud eRDMA (erdma_*), NVSHMEM cannot loadlibmlx5dv; the log says that directNIC features are disabled, but the low-latency path is not usable. The existing guide only says “RDMA devices” and “IBGDA”, which can make this look like a recoverable warning.Change
mlx5eRDMA as unsupported for V1 internode and low-latency examples.Validation
git diff --check../README.mdrelative link.Fixes #759
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.