Skip to content

Clarify cl_khr_external_memory_win32 import behavior #1310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joshqti opened this issue Feb 10, 2025 · 2 comments
Open

Clarify cl_khr_external_memory_win32 import behavior #1310

joshqti opened this issue Feb 10, 2025 · 2 comments

Comments

@joshqti
Copy link
Contributor

joshqti commented Feb 10, 2025

Clarify the behavior when importing NT handles, and the image or buffer is from a different vendor than the OpenCL implementation.

@bashbaug
Copy link
Contributor

bashbaug commented Apr 1, 2025

Discussed in the April 1st memory subgroup. This may be a more general issue about cross-adapter sharing.

@bashbaug bashbaug moved this from To do to Needs WG discussion in OpenCL specification maintenance Apr 1, 2025
@bashbaug
Copy link
Contributor

Discussed in the April 22nd memory subgroup. Currently, the only way this could work is with linear layout, though extensions in flight may help to make this more robust (e.g. DRM format modifiers). We will consider adding an informative note to the spec for now to reduce confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs WG discussion
Development

No branches or pull requests

2 participants