[GH-ISSUE #488] Question About num_rc_per_pe in Normal Dispatch #316

Closed
opened 2026-10-26 09:58:30 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @michaelchen1996 on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/488

https://github.com/deepseek-ai/DeepEP/pull/181 fixed a timeout problem by forbidding concurrent submissions of QP.

However, in normal dispatch

EP_DEVICE_ASSERT(ibgda_get_state()->num_rc_per_pe == num_channels or ibgda_get_state()->num_rc_per_pe >= num_sms);

Why is num_rc_per_pe == num_channels still allowed?

Thank you!

Originally created by @michaelchen1996 on GitHub (Nov 10, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/488 https://github.com/deepseek-ai/DeepEP/pull/181 fixed a timeout problem by forbidding concurrent submissions of QP. However, in normal dispatch ``` EP_DEVICE_ASSERT(ibgda_get_state()->num_rc_per_pe == num_channels or ibgda_get_state()->num_rc_per_pe >= num_sms); ``` Why is `num_rc_per_pe == num_channels` still allowed? Thank you!
Author
Owner

@sphish commented on GitHub (Nov 12, 2025):

This PR does not actually fix the underlying issue; it only increases the number of QPs, which leads to better performance. The original QP configuration is still functional, and to maintain forward compatibility, we have kept the original QP settings in the assertions.

<!-- gh-comment-id:3519700919 --> @sphish commented on GitHub (Nov 12, 2025): This PR does not actually fix the underlying issue; it only increases the number of QPs, which leads to better performance. The original QP configuration is still functional, and to maintain forward compatibility, we have kept the original QP settings in the assertions.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepEP#316
No description provided.