CLCREATEFROMD3D11TEX(3clc)

📦
version 1.0~svn33624 · 3 versions
, in ubuntu jammy, ubuntu noble

💖 CLCREATEFROMD3D11TEX(3clc) 💖

from the OpenCL Manual, bestie — yes the whole manual name, we're being official today ✨

✨ NAME ✨

clCreateFromD3D11Texture2DKHR — creates an OpenCL 2D image object from a subresource of a Direct3D 11 2D texture. 🎀

cl_mem clCreateFromD3D11Texture2DKHR(cl_context context,
                                     cl_mem_flags flags,
                                     ID3D11Texture2D *resource,
                                     UINT subresource,
                                     cl_int *errcode_ret);

🌸 PARAMETERS 🌸

  • context — a valid OpenCL context, and it has to be one created from a Direct3D 11 device. no random contexts allowed, she's picky 💅
  • flags — a bit-field that specifies usage info. may be CL_MEM_READ_ONLY, CL_MEM_WRITE_ONLY, or CL_MEM_READ_WRITE. (there's a whole table over in clCreateBuffer(3clc) if you want the deep lore 🧚)
  • resource — a pointer to the Direct3D 11 2D texture you wanna share. 🦋
  • subresource — the subresource of resource that's getting shared. yes bestie, just the one. 👑
  • errcode_ret — an appropriate error code. and if errcode_ret is NULL, then no error code comes back at all. 🙈

🔥 NOTES 🔥

okay so the width, height and depth of the returned OpenCL 2D image object are determined by the width, height and depth of subresource subresource of resource. and the channel type and order of the returned OpenCL 2D image object is determined by the format of resource as shown in of Direct3D 11 and corresponding OpenCL image formats of resource in clCreateFromD3D11Texture3DKHR(3clc). 🌈

this call will increment the internal Direct3D reference count on resource. and that internal Direct3D reference count on resource gets decremented when the OpenCL reference count on the returned OpenCL memory object drops to zero. it's giving very balanced-books energy ✨

general info about sharing memory objects with Direct3D 11 follows, bestie:

the goal of this extension is to provide interoperability between OpenCL and Direct3D 11. it's designed to function analogously to the OpenGL interoperability. and if this extension is supported by an implementation, the string cl_khr_d3d11_sharing(3clc) 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_d3d11.h.

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. (if and only if, bestie. she said what she said 💅)

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 CL_CONTEXT_D3D11_DEVICE_KHR 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.

properties of Direct3D 11 objects may be queried using clGetMemObjectInfo(3clc) and clGetImageInfo(3clc) with param_name CL_MEM_D3D11_RESOURCE_KHR and CL_IMAGE_D3D11_SUBRESOURCE_KHR as described for clGetImageInfo(3clc) and in the information below about accessing mapped regions of a memory object. Accessing mapped regions of a memory object.PP This section describes the behavior of OpenCL commands that access mapped regions of a memory object. 👀

the contents of the region of a memory object and associated memory objects (sub-buffer objects or 1D image buffer objects that overlap this region) mapped for writing (i.e. CL_MAP_WRITE or CL_MAP_WRITE_INVALIDATE_REGION is set in map_flags argument to clEnqueueMapBuffer(3clc) or clEnqueueMapImage(3clc)) are considered to be undefined until this region is unmapped. 🌸

multiple commands in command-queues can map a region or overlapping regions of a memory object and associated memory objects (sub-buffer objects or 1D image buffer objects that overlap this region) for reading (i.e. map_flags = CL_MAP_READ). the contents of the regions of a memory object mapped for reading can also be read by kernels and other OpenCL commands (such as clEnqueueCopyBuffer(3clc)) executing on a device(s). ✨

😭 mapping (and unmapping) overlapped regions in a memory object and/or associated memory objects (sub-buffer objects or 1D image buffer objects that overlap this region) for writing is an error and will result in CL_INVALID_OPERATION error returned by clEnqueueMapBuffer(3clc) or clEnqueueMapImage(3clc).

if a memory object is currently mapped for writing, the application must ensure that the memory object is unmapped before any enqueued kernels or commands that read from or write to this memory object or any of its associated memory objects (sub-buffer or 1D image buffer objects) or its parent object (if the memory object is a sub-buffer or 1D image buffer object) begin execution; otherwise the behavior is undefined. 💀

if a memory object is currently mapped for reading, the application must ensure that the memory object is unmapped before any enqueued kernels or commands that write to this memory object or any of its associated memory objects (sub-buffer or 1D image buffer objects) or its parent object (if the memory object is a sub-buffer or 1D image buffer object) begin execution; otherwise the behavior is undefined. 💀

accessing the contents of the memory region referred to by the mapped pointer that has been unmapped is undefined. 🙈

the mapped pointer returned by clEnqueueMapBuffer(3clc) or clEnqueueMapImage(3clc) can be used as ptr argument value to clEnqueueReadBuffer(3clc), clEnqueueWriteBuffer(3clc), clEnqueueReadBufferRect(3clc), clEnqueueWriteBufferRect(3clc), clEnqueueReadImage(3clc), and clEnqueueWriteImage(3clc), provided the rules described above are adhered to. 🫶

💅 ERRORS 💅

Returns CL_SUCCESS returns a valid non-zero OpenCL image object and errcode_ret is set to CL_SUCCESS if the image object is created successfully. otherwise, it returns a NULL value with one of the following error values returned in errcode_ret:

  • CL_INVALID_CONTEXT — if context is not a valid context. 😭
  • CL_INVALID_VALUE — if values specified in flags are not valid or if subresource is not a valid subresource index for resource. 🙈
  • CL_INVALID_D3D11_RESOURCE_KHR — if resource is not a Direct3D 11 texture resource, if resource was created with the D3D11_USAGE flag D3D11_USAGE_IMMUTABLE, if a resource is a multisampled texture, if cl_mem from subresource subresource of resource has already been created using clCreateFromD3D11Texture2DKHR, or if context was not created against the same Direct3D 11 device from which resource was created. 💀
  • CL_INVALID_D3D11_RESOURCE_KHR — if resource is not a Direct3D 11 texture object. (yes bestie, she's listed twice, that's just how it is 💖)
  • CL_INVALID_IMAGE_FORMAT_DESCRIPTOR — if the Direct3D 11 texture format of resource is not a value listed in the table of Direct3D 11 and corresponding OpenCL image formats for clCreateFromD3D11Texture3DKHR(3clc), or if the Direct3D 11 texture format of resource does not map to a supported OpenCL image format. 🎀
  • CL_OUT_OF_HOST_MEMORY — if there is a failure to allocate resources required by the OpenCL implementation on the host. 😭

🌈 SPECIFICATION 🌈

OpenCL Specification[1] ⭐

🦋 SEE ALSO 🦋

👑 AUTHORS 👑

The Khronos Group ✨

Copyright © 2007-2011 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. 🫶

🎀 NOTES 🎀

  1. OpenCL Specification page 105, section 9.11.7.4 - Sharing Direct3D 11 Texture and Resources... 📖

and that's the whole page, bestie!! 💅✨ this one came from The Khronos Group, dated 01/14/2021, under the manual name CLCREATEFROMD3D11TEX(3clc) — go forth and share your Direct3D 11 2D textures responsibly, no cap 🎀🦋💖

📦 where this page comes from