[SYCL][Doc][L0] Add restrctions to interop API #19588
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to align with the v2 adapter implementation. The v2 adapter operates exclusively on in-order command-lists. This means that it cannot support arbitrary command queue/handle provided by the user. With the new restrictions, the adapter can choose to create a new command-list (with the same properties as the handle passed by the user) and use that instead. This means that it is no longer possible to synchronize with the native handle (e.g. by submitting a barrier) directly. The only mechanism left is native events.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to align with the v2 adapter implementation.
The v2 adapter operates exclusively on in-order command-lists. This means that it cannot support arbitrary command queue/handle provided by the user. With the new restrictions, the adapter can choose to create a new command-list (with the same properties as the handle passed by the user) and use that instead.
This means that it is no longer possible to synchronize with the native handle (e.g. by submitting a barrier) directly. The only mechanism left is native events.