Description
If the cl_khr_d3d10_sharing extension is supported, then the
following functions are enabled:
General information about sharing memory objects with Direct3D 10 follows.
The goal of this extension is to provide interoperability between
OpenCL and Direct3D 10. This is designed to function analogously
to the OpenGL
interoperability 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
(see clGetPlatformInfo)
or CL_DEVICE_EXTENSIONS
(see clGetDeviceInfo).
As currently proposed the interfaces for this extension would be provided in
cl_d3d10.h.
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.
Lifetime of Shared [D3D10] Objects
An OpenCL memory object created from a Direct3D 10 resource remains valid as long as the corresponding Direct3D 10 resource has not been deleted. If the Direct3D 10 resource is deleted through the Direct3D 10 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 10 device specified via the context
create parameter CL_CONTEXT_D3D10_DEVICE_KHR will increment the internal Direct3D
reference count on the specified Direct3D 10 device. The internal Direct3D reference count on
that Direct3D 10 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 10 device from which the OpenCL context was created. If the Direct3D 10 device is deleted through the Direct3D 10 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.
Copyright © 2007-2013 The Khronos Group Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and/or associated documentation files (the
"Materials"), to deal in the Materials without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Materials, and to
permit persons to whom the Materials are furnished to do so, subject to
the condition that this copyright notice and permission notice shall be included
in all copies or substantial portions of the Materials.