KhronosGroup / KhronosGroup/OpenCL-Docs

When is it safe to create an OpenCL buffer from a Unified SVM allocation

Open
#1,603 2 comments 0 reactions 0 assignees View on GitHub
cl_khr_unified_svm
Dominant language
Python
Stars
420
Forks
131
Avg merge
5d 13h
Merged PRs (30d)
11

Description

We need to reconcile the behavior of pointers created with the legacy SVMAlloc() command with pointers created using clSVMAllocWithPropertiesKHR() when it comes to creating buffers using the CL_MEM_USE_HOST_PTR flag.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the documented behavior of legacy SVMAlloc(), clSVMAllocWithPropertiesKHR(), and CL_MEM_USE_HOST_PTR in the OpenCL documentation. Done means the rules for creating buffers from each kind of Unified SVM allocation are reconciled and stated unambiguously.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.