deepseek-ai/DeepGEMM
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepGEMM.git synced 2026-11-05 00:47:26 +00:00
Code Issues 162 Projects Packages Wiki Activity

[GH-ISSUE #289] Question about the scale factor layout #145

New issue
Closed
opened 2026-10-26 21:13:40 +00:00 by bsakaguchi · 1 comment
bsakaguchi commented 2026-10-26 21:13:40 +00:00
Owner
Copy link

Originally created by @Yyf1023 on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/289

Recently I am reading the code of sm100 fp8 GEMM. I have a question:
Why must the scale factor be MN-major? Is it because this provides better performance or is it due to hardware constraints? Thank you for your reply.

Originally created by @Yyf1023 on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/289 Recently I am reading the code of sm100 fp8 GEMM. I have a question: Why must the scale factor be MN-major? Is it because this provides better performance or is it due to hardware constraints? Thank you for your reply.
bsakaguchi commented 2026-10-26 21:13:41 +00:00
Author
Owner
Copy link

@zheanxu commented on GitHub (Apr 17, 2026):

Hi! This is because every time TMA loads the scale factors, it needs to load a tile of block_m * 1 or block_n * 1. This requires the scale factor data to be contiguous along the M or N dimension, hence the MN-major layout requirement.

<!-- gh-comment-id:4264896766 --> @zheanxu commented on GitHub (Apr 17, 2026): Hi! This is because every time TMA loads the scale factors, it needs to load a tile of `block_m * 1` or `block_n * 1`. This requires the scale factor data to be contiguous along the M or N dimension, hence the MN-major layout requirement.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
public-sync-20261014
0930-release
nv_dev
fix-mega-moe-fence
public-release-2609
public-release-2607
public-release-2606
mega-update
public-release-260416
ko3n1g/ci/build-wheels
nv_dev_f8e8fb5
nv_dev_950d31a
nv_dev_67fc648
nv_dev_c491439
nv_dev_4ff3f54
v2.1.1.post3
v2.1.1.post2
v2.1.1.post1
v2.1.1
v2.1.0
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/DeepGEMM#145
No description provided.