Skip to content
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.

Sign up for GitHub

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

[RFC] Say something about asynchronous behavior on host #685

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[RFC] Say something about asynchronous behavior on host #685

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions adoc/chapters/architecture.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -441,6 +441,16 @@ The SYCL implementation guarantees the correct initialization and destruction of
any resource handled by the underlying <<backend-api>>, except for those the
user has obtained manually via the SYCL interoperability API.

==== Synchronous and asynchronous resource management

A SYCL implementation may manage <<backend-api>> resources synchronously by
calling into the <<backend-api>> in the same host thread that the SYCL
application uses to call into SYCL.
A SYCL implementation may also manage <<backend-api>> resources asynchronously,
using a host thread owned by the SYCL implementation.
It is implementation-defined whether a given interaction between the
<<sycl-runtime>> and a <<backend-api>> occurs synchronously or asynchronously.

[[sec:command-groups-exec-order]]
==== SYCL command groups and execution order

Expand Down
Loading