CL_KHR_D3D11_SHARING(3clc)
π CL_KHR_D3D11_SHARING π
okay bestie, welcome to the CL_KHR_D3D11_SHARING(3clc) page from the OpenCL Manual β¨ this is the one about making OpenCL and Direct3D 11 be friends. yes, it's giving crossover episode energy π
πΈ NAME πΈ
cl_khr_d3d11_sharing β provide interoperability between OpenCL and Direct3D 11 π¦
#pragma OPENCL EXTENSION
cl_khr_d3d11_sharing : enable
like, that's the whole vibe. you turn it on with that pragma and suddenly your two GPU worlds are holding hands π«Ά
β¨ DESCRIPTION β¨
So the goal of this extension is to provide interoperability between OpenCL and Direct3D 11, and it's designed to function analogously to cl_khr_gl_sharing(3clc) as defined in sections 9.7 and 9.8 π no cap.
If an implementation supports this extension, then the string
"cl_khr_d3d11_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) π
so that's your vibe check right there β go look for that string and you'll know.
The interfaces for this extension are provided in the header file cl_d3d11.h π
If the cl_khr_d3d11_sharing extension is supported, then the following functions are enabled:
The OpenCL functions enabled by the cl_khr_d3d11_sharing extension allow applications to use Direct3D 11 resources as OpenCL memory objects π which is the whole point, and it 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. π
and here's the rule, bestie, do NOT skip it: 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. that's not a suggestion, that's the law π
π SPECIFICATION π
OpenCL Specification[1] β
π SEE ALSO π
EXTENSION(3clc), clGetDeviceIDsFromD3D11KHR(3clc), clCreateFromD3D11BufferKHR(3clc), clCreateFromD3D11Texture2DKHR(3clc), clCreateFromD3D11Texture3DKHR(3clc), clEnqueueAcquireD3D10ObjectsKHR(3clc), clEnqueueReleaseD3D11ObjectsKHR(3clc)
(no shade to the D3D10 one sitting in there, it's just how the list is, iykyk π)
π«Ά AUTHORS π«Ά
The Khronos Group π
π COPYRIGHT π
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 π¦
- OpenCL Specification page 97, section 9.11 - Sharing Memory Objects with Direct3D 11
and that's the page!! πβ¨ brought to you by The Khronos Group, dated 01/14/2021 β mwah, iconic, periodt ππ¦πΈπ
π¦ where this page comes from
- ubuntu jammy: opencl-1.2-man-doc 1.0~svn33624-5 Β· other
- ubuntu noble: opencl-1.2-man-doc 1.0~svn33624-5 Β· other
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms