cl_int clEnqueueReleaseD3D11ObjectsKHR(cl_command_queue command_queue,
const cl_mem *mem_objects,
const cl_event *event_wait_list,
num_objects - The number of memory objects to be released in mem_objects.
mem_objects - A pointer to a list of OpenCL memory objects that were created from Direct3D 11 resources.
num_events_in_wait_list - Number of events in event_wait_list.
event_wait_list - Specify events that need to complete before this particular command can be executed. If event_wait_list is NULL, then this particular command does not wait on any event to complete. If event_wait_list is NULL, num_events_in_wait_list must be 0. If event_wait_list is not NULL, the list of events pointed to by event_wait_list must be valid and num_events_in_wait_list must be greater than 0.
event returns an event object that identifies this command and can be used to query or wait for this command to complete. If event is
NULLor the enqueue is unsuccessful, no event will be created and therefore it will not be possible to query the status of this command or to wait for this command to complete. If event_wait_list and event are not
NULL, event must not refer to an element of the event_wait_list array.
The Direct3D 11 objects are released by the OpenCL context associated with command_queue.
OpenCL memory objects created from Direct3D 11 resources which have been acquired by OpenCL must be released by OpenCL before they may be accessed by Direct3D 11. Accessing a Direct3D 11 resource while its corresponding OpenCL memory object is acquired is in error and will result in undefined behavior, including but not limited to possible OpenCL errors, data corruption, and program termination.
CL_CONTEXT_INTEROP_USER_SYNC is not specified as
CL_TRUE during context creation,
clEnqueueReleaseD3D11ObjectsKHR provides the synchronization guarantee that any calls to Direct3D 11 calls involving the interop device(s) used in the OpenCL context made after the call to
clEnqueueReleaseD3D11ObjectsKHR will not start executing until after all events in event_wait_list are complete and all work already submitted to command_queue completes execution.
If the context was created with properties specifying
CL_TRUE, the user is responsible for guaranteeing that any Direct3D 11 calls involving the interop device(s) used in the OpenCL context made after
clEnqueueReleaseD3D11ObjectsKHR will not start executing until after event returned by
clEnqueueReleaseD3D11ObjectsKHR reports completion.
The goal of this extension is to provide interoperability between OpenCL and
Direct3D 11. This is designed to function analogously to the
cl_khr_gl_sharing as defined in sections 9.7 and 9.8. If this
extension is supported by an implementation, the string
"cl_khr_d3d11_sharing" will be present in the
CL_DEVICE_EXTENSIONS string described in the table of allowed values for
param_name for clGetDeviceInfo or clGetPlatformInfo.
As currently proposed the interfaces for this extension would be provided in
This section discusses OpenCL functions that allow applications to use Direct3D 11 resources as OpenCL memory objects. This allows efficient sharing of data between OpenCL and Direct3D 11. The OpenCL API may be used to execute kernels that read and/or write memory objects that are also Direct3D 11 resources. An OpenCL image object may be created from a Direct3D 11 texture resource. An OpenCL buffer object may be created from a Direct3D 11 buffer resource. OpenCL memory objects may be created from Direct3D 11 objects if and only if the OpenCL context has been created from a Direct3D 11 device.
An OpenCL memory object created from a Direct3D 11 resource remains valid as long as the corresponding Direct3D 11 resource has not been deleted. If the Direct3D 11 resource is deleted through the Direct3D 11 API, subsequent use of the OpenCL memory object will result in undefined behavior, including but not limited to possible OpenCL errors, data corruption, and program termination.
The successful creation of a
cl_context against a Direct3D 11 device
specified via the context create parameter
will increment the internal Direct3D reference count on the specified
Direct3D 11 device. The internal Direct3D reference count on that Direct3D
11 device will be decremented when the OpenCL reference count on the
returned OpenCL context drops to zero.
The OpenCL context and corresponding command-queues are dependent on the existence of the Direct3D 11 device from which the OpenCL context was created. If the Direct3D 11 device is deleted through the Direct3D 11 API, subsequent use of the OpenCL context will result in undefined behavior, including but not limited to possible OpenCL errors, data corruption, and program termination.
CL_SUCCESS if the function is executed successfully.
If num_objects is 0 and mem_objects is NULL the function does nothing and returns
Otherwise it returns one of the following errors:
CL_INVALID_VALUEif num_objects is zero and mem_objects is not a NULL value or if num_objects > 0 and mem_objects is NULL.
CL_INVALID_MEM_OBJECTif memory objects in mem_objects are not valid OpenCL memory objects or if memory objects in mem_objects have not been created from Direct3D 11 resources.
CL_INVALID_COMMAND_QUEUEif command_queue is not a valid command-queue.
CL_INVALID_CONTEXTif context associated with command_queue was not created from a Direct3D 11 device.
CL_D3D11_RESOURCE_NOT_ACQUIRED_KHRif memory objects in mem_objects have not previously been acquired using clEnqueueAcquireD3D11ObjectsKHR, or have been released using
clEnqueueReleaseD3D11ObjectsKHRsince the last time that they were acquired.
CL_INVALID_EVENT_WAIT_LISTif event_wait_list is NULL and
num_event_in_wait_list> 0, or event_wait_list is not NULL and
num_event_in_wait_listis 0, or if event objects in event_wait_list are not valid events.
CL_OUT_OF_HOST_MEMORYif there is a failure to allocate resources required by the OpenCL implementation on the host.
For more information, see the OpenCL Extension Specification at URL