-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL][UR][L0 v2] implement OOO immediate queue #18903
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just two minor questions
unified-runtime/source/adapters/level_zero/v2/queue_immediate_out_of_order.cpp
Outdated
Show resolved
Hide resolved
unified-runtime/source/adapters/level_zero/v2/queue_immediate_out_of_order.cpp
Outdated
Show resolved
Hide resolved
unified-runtime/source/adapters/level_zero/v2/queue_immediate_out_of_order.cpp
Outdated
Show resolved
Hide resolved
unified-runtime/source/adapters/level_zero/v2/queue_immediate_out_of_order.hpp
Outdated
Show resolved
Hide resolved
unified-runtime/source/adapters/level_zero/v2/queue_immediate_out_of_order.hpp
Show resolved
Hide resolved
unified-runtime/source/adapters/level_zero/v2/queue_immediate_out_of_order.cpp
Outdated
Show resolved
Hide resolved
unified-runtime/source/adapters/level_zero/v2/command_buffer.cpp
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SYCL E2E changes LGTM.
@intel/llvm-gatekeepers this is ready to be merged, the OPENCL issues are unrelated (fixed in: #19138) |
by using multiple in-order queues and round-robin strategy to dispatch work. With this approach we don't need to worry about events' lifetime. Since we are still using counter-based events, we don't need any special logic to handle cases where event release is called right after being passed as signal event or as part of a wait list.
🚀 🚀 🚀 🚀 🚀 |
by using multiple in-order queues and round-robin
strategy to dispatch work.
With this approach we don't need to worry about events' lifetime. Since we are still using counter-based events, we don't need any special logic to handle cases where event release is called right after being passed as signal event or as part of a wait list.