Further explanation for batch_isend_irecv
#125099
Labels
oncall: distributed
Add this issue/PR to distributed oncall triage queue
triaged
This issue has been looked at a team member, and triaged and prioritized into an appropriate module
馃摎 The doc issue
here the doc string says the function will return
dist.Work
by calling corresponding ops, however the returned reqs might not be "corresponding" (e.g.batch_isend_irect([op1, op2])
might return only one[coalescing_req]
), which is quite confusing. (Or can we have a 1-to-1 mapping for p2p_op_list and returned reqs?Suggest a potential alternative/fix
No response
cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @d4l3k
The text was updated successfully, but these errors were encountered: