mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #298] how to understand the rdma buffer #211
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#211
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 @kzlxd on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/298
Each rank has its own rdma_buffer_ptr, which rank's rdma buffer will be used for rdma transfers, and will only nvl rank 0's rdma buffer be selected?
@sphish commented on GitHub (Jul 15, 2025):
Which RDMA rank you want to send to/recv from, you need to use the RDMA buffer of that RDMA rank.
@kzlxd commented on GitHub (Jul 15, 2025):
During the data transfer of the kRDMAReceiver, only data from different rdma ranks were combine. There is no local rank distribution. Is it possible to understand that the sender knows which rank to send to @sphish
@sphish commented on GitHub (Jul 15, 2025):
Yes
@kzlxd commented on GitHub (Jul 15, 2025):
Does the rdma recv_buffer of a rank in normal mode map to the location of the same card number on the opposite node? @sphish