[QST] Details of Auto Schedule Execution Strategy on Blackwell
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
On the Blackwell architecture, which is preferred to use Auto Schedule. When running GEMM with Auto Schedule, how many SMs does the scheduler actually assign to the kernel? Does Auto Schedule internally make use of Distributed Shared Memory (DSMEM), and is there a way to inspect this?
Background:
I am currently running into an issue on Blackwell where I explicitly set cluster<_1, _1, _1>, so the kernel should be using only a single CTA cluster. However, when debugging and printing out the shared memory addresses, it appears as if two clusters are involved.
This makes me wonder:
-
Does Auto Schedule internally change the number of SMs assigned to the kernel?
-
Can Auto Schedule implicitly increase the number of clusters, even when the user specifies cluster<1,1,1>?
-
If DSMEM is being used implicitly, how can we confirm or inspect this behavior?
Any clarification on how Auto Schedule interacts with SM assignment and cluster configuration on Blackwell would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Auto Schedule GEMM execution, SM assignment, CTA clusters, and DSMEM on Blackwell but does not identify files or tests. Start by locating the Auto Schedule GEMM entry point and cluster configuration, then determine how the configured cluster count and DSMEM usage can be inspected; done means documenting the observed behavior and inspection path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- backend, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100