mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #92] Will the Normal Kernel (dispatch kernel) exclusively occupy the SM of the GPU? #84
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#84
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 @PhilipJohnson2 on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/92
In the dispatch definition, each block has 512 threads. During actual execution, can we ensure that each block of the dispatch kernel exclusively occupies one SM through resource constraints such as register limits?
@LyricZhao commented on GitHub (Mar 26, 2025):
Yes, the register usage is spilling for almost all kernels, and we also have things like
__launch_bounds__(kNumThreads, 1)to tell 1 block per SM. So this is exclusive.