cl_khr_d3d10_sharing3clc
Provide interoperability between opencl and direct3d 10.
Overview
The goal of this extension is to provide interoperability between OpenCL and Direct3D 10. This is designed to function analogously to the cl_khr_gl_sharing(3clc) as defined in sections 9.7 and 9.8. If this extension is supported by an implementation, the string "cl_khr_d3d10_sharing" will be present in the CL_PLATFORM_EXTENSIONS or CL_DEVICE_EXTENSIONS string described in the table of allowed values for param_name for clGetDeviceInfo(3clc).
As currently proposed the interfaces for this extension would be provided in cl_d3d10.h.
If the cl_khr_d3d10_sharing extension is supported, then the following functions are enabled:
• clGetDeviceIDsFromD3D10KHR(3clc).RE
• clCreateFromD3D10BufferKHR(3clc).RE
• clCreateFromD3D10Texture2DKHR(3clc).RE
• clCreateFromD3D10Texture3DKHR(3clc).RE
• clEnqueueAcquireD3D10ObjectsKHR(3clc).RE
• clEnqueueReleaseD3D10ObjectsKHR(3clc).RE
The OpenCL functions enabled by the cl_khr_d3d10_sharing extension allow applications to use Direct3D 10 resources as OpenCL memory objects. This allows efficient sharing of data between OpenCL and Direct3D 10. The OpenCL API may be used to execute kernels that read and/or write memory objects that are also Direct3D 10 resources. An OpenCL image object may be created from a Direct3D 10 texture resource. An OpenCL buffer object may be created from a Direct3D 10 buffer resource. OpenCL memory objects may be created from Direct3D 10 objects if and only if the OpenCL context has been created from a Direct3D 10 device.
Specification
OpenCL Specification[1]
Notes
- 1.
-
OpenCL Specification
page 66, section 9.9 - Sharing Memory Objects with Direct3D 10
Releases
5 releases since Debian 8 (Jessie); the text changed 3 times.