You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a wait is called on the queue inside the graph immediately after enqueue. Examples which attempt to wait on the event returned from the graph submission will fail without this wait occuring. This should be investigated so that we can remove the queue wait from graph submission.
The text was updated successfully, but these errors were encountered:
Bensuo
changed the title
Waiting on events returned from graph submission does not work
Waiting on events returned from executable graph submission does not work
Apr 13, 2023
The current approach uses the same LO PI event for all submissions
of the same graph, and also doesn't use the wait events to
enforce dependencies on the command-list submission. By doing these
in the L0 adapter, we can remove the blocking queue wait from
our graphs submission code in the runtime.
Closes issue #139
The current approach uses the same LO PI event for all submissions
of the same graph, and also doesn't use the wait events to
enforce dependencies on the command-list submission. By doing these
in the L0 adapter, we can remove the blocking queue wait from
our graphs submission code in the runtime.
Closes issue #139
The current approach uses the same LO PI event for all submissions
of the same graph, and also doesn't use the wait events to
enforce dependencies on the command-list submission. By doing these
in the L0 adapter, we can remove the blocking queue wait from
our graphs submission code in the runtime.
Closes issue #139
Currently a wait is called on the queue inside the graph immediately after enqueue. Examples which attempt to wait on the event returned from the graph submission will fail without this wait occuring. This should be investigated so that we can remove the queue wait from graph submission.
The text was updated successfully, but these errors were encountered: