mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #467] Questions About AR Support for Low-latency #301
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#301
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 @michaelchen1996 on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/467
Commit: 2d0cf41dd1900b105d74cb071f4cac35e3fb6f47
Low latency kernels use rdma atomic to support AR.
This commit replaces two functions:
nvshmemi_ibgda_rma_pnvshmemi_ibgda_poll_recvwith a new function:
nvshmemi_ibgda_amo_nonfetch_add
From code inspection,
nvshmemi_ibgda_rma_pappears to use RDMA Write with Immediate Data.Does RDMA Write with IMM not support AR? Why we have to use
nvshmemi_ibgda_amo_nonfetch_addto add AR support for low-latency ?Thank you!
@michaelchen1996 commented on GitHub (Oct 27, 2025):
Additionally, may I ask that if this is because NVSHMEM does not have a write with imm operation, why is
nvshmemi_ibgda_rma_pwith theimmparameter still retained?