Why cutile's rmsnorm required full register
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 811
- Forks
- 87
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 9
Description
I just test 16384x512 bf16 dtype rmsnorm, Nsight compute report says rms_norm_kernel_static_persistent use 255 registers, and I wonder how to control register num to increase occupancy.
Contributor guide
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 by locating the implementation of rms_norm_kernel_static_persistent and reproduce the 16384x512 bf16 rmsnorm case. Use Nsight Compute to inspect its 255-register usage and occupancy. Done means identifying why the kernel uses the full register allocation and documenting or demonstrating how register usage can be controlled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100