[QST]Do we need to tune cutlass gemm to use it for all shape?
Open
Nobody has claimed this yet.
? - Needs Triage
inactive-90d
question
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
I see the example here, https://github.com/NVIDIA/cutlass/blob/main/examples/00_basic_gemm/basic_gemm.cu
It doesn't requires the config for tile size, grid size, warp size etc.
My question is that:
- Does it look for the best config automatically ? Or do I just get a kernel with default config?
- Do I need to tune it when using it for dynamic shapes? How to do that?
Thank you!
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
Start with the linked CUTLASS example at examples/00_basic_gemm/basic_gemm.cu and compare its GEMM configuration with the questions in this issue. Clarify whether the example selects defaults or searches configurations, and document what tuning dynamic shapes requires; done means both questions have an authoritative answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100