Potential problem with zeKernelSuggestGroupSize

Open
#124 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
api

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.

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 ?

Dominant language
C++
Stars
335
Forks
140
Avg merge
12h 32m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oneapi-src/level-zero

All issues in oneapi-src/level-zero

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.