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.

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

[SYCL][Graph] Clarify graph in-order and out-of-order properties #370

Closed
wants to merge 2 commits into from
Closed
Changes from 1 commit
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -666,6 +666,14 @@ operation as the runtime can perform optimizations based on the graph
structure. After finalization the graph can be submitted for execution on a
queue one or more times with reduced overhead.

A `command_graph` can be submitted to both in-order and out-of-order queues. Any
dependencies between the graph and other command-groups submitted to the same
queue will be respected. However, the in-order and out-of-order properties of the
queue have no effect on how the graph itself is executed (e.g. the graph nodes
might execute out-of-order even when using an in-order queue). For further
EwanC marked this conversation as resolved.
Show resolved Hide resolved
information about the interaction between queues and graphs
<<Queue Class Modifications, see the section on Queue Class Modifications>>
EwanC marked this conversation as resolved.
Show resolved Hide resolved

==== Graph State

An instance of a `command_graph` object can be in one of two states:
Expand Down