mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[GH-ISSUE #152] Question about overlapping between promotion and wgmma #88
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/DeepGEMM#88
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 @pengwubj on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/152
Why isn't a barrier used to establish a deterministic execution order between two warpgroups, so that promotion can be well hidden within the matrix computation? While studying CUTLASS, I found that the ping-pong approach uses
OrderedSequenceBarrierto serialize the execution of two warpgroups, and for example, FA3 usesNamedBarrierto coordinate between two warpgroups(FLashMLA in same way)。Of course, it seems that this can also be automatically achieved based on NVIDIA hardware's greedy warp scheduling strategy and FFMA interleave technology.Could you share your insight and experience about this ? Thanks a lot!
@LyricZhao commented on GitHub (Aug 14, 2025):
Barrier/sync costs a lot, we don't exchage data between two warpgroups. The overlapping is done by hardware warp scheduler.
@pengwubj commented on GitHub (Aug 14, 2025):
Thanks a lot !