oneapi-src / oneapi-src/level-zero
Potential problem with zeKernelSuggestGroupSize
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Description
My use case is that I have a buffer to be processed of a size 2^40 and I want to use zeKernelSuggestGroupSize to get
optimal setting of work group to be used. Problem is that spec claims that globalSizeX is of u32 type and this is not enough to hold 2^40 value. My spirv is processng linearly whole buffer (elementwise operation). So shouldn't zeKernelSuggestGroupSize's args globalSizeX, globalSizeY,globalSizeZ be of type of u64 or size_t ?
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 with the linked Level Zero specification entry for zeKernelSuggestGroupSize and review the globalSizeX, globalSizeY, and globalSizeZ definitions. Check how the stated u32 types relate to the reported 2^40 elementwise workload and determine whether the concern requires an API or specification change. Done means the width decision and its implications are clearly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100