KhronosGroup / KhronosGroup/OpenCL-Docs
Does the image total size need to be restricted by CL_DEVICE_MAX_MEM_ALLOC_SIZE?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 132
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
In Spec 3.0, clCreateBuffer and clSVMAlloc will return error if size is greater than CL_DEVICE_MAX_MEM_ALLOC_SIZE.
Why does clCreateImage not have this constraint? Is there any special consideration?
as I know, image is also a mem object like buffer.
In addition to the existed dimensions size check in spec, Is it reasonableto to return CL_INVALID_IMAGE_SIZE if image total size exceed CL_DEVICE_MAX_MEM_ALLOC_SIZE.
Thanks!
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
Review the Spec 3.0 rules for clCreateBuffer, clSVMAlloc, and clCreateImage, focusing on the existing size and dimension constraints. Determine whether image total size should be limited by CL_DEVICE_MAX_MEM_ALLOC_SIZE and what specification change would be required; the issue provides no named source file or test.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100