-
Notifications
You must be signed in to change notification settings - Fork 796
[UR][L0] Event cleanup in urEnqueueKernelLaunch #19827
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
90e5349 to
ea87fce
Compare
3d95223 to
ebea5a0
Compare
809c0c5 to
ebc5c20
Compare
ebc5c20 to
f9a2eeb
Compare
f9a2eeb to
c7a28d2
Compare
88e1d22 to
c01fc27
Compare
When using internal events we do not clean up after execution. In the case of repeated call to urEnqueueKernelLaunch we eventually return UR_RESULT_ERROR_OUT_OF_RESOURCES. The cleanup is done when we call zeEventPoolCreate. Signed-off-by: Zhang, Winston <[email protected]>
Signed-off-by: Zhang, Winston <[email protected]>
Signed-off-by: Zhang, Winston <[email protected]>
c01fc27 to
6680836
Compare
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.
LGTM, the CI failure is a build issue unrelated to this change.
|
@intel/llvm-gatekeepers Patch is ready. Please merge when possible. Thanks! |
|
@intel/llvm-gatekeepers , please merge when available, the issue in the CI is a build issue unrelated to this change. |
|
Yep that issue should be fixed in HEAD, definitely unrelated/ |
When using internal events we do not clean up after execution. In the case of repeated call to urEnqueueKernelLaunch we eventually return UR_RESULT_ERROR_OUT_OF_RESOURCES. --------- Signed-off-by: Zhang, Winston <[email protected]>
This is a joint cherry-pick of #18325 and #19827 --- [UR][L0] Event pool cache leak fix (#18325) addresses event pool leak when SYCL_PI_LEVEL_ZERO_DISABLE_EVENTS_CACHING is set to 1 --- [UR][L0] Event cleanup in urEnqueueKernelLaunch (#19827) When using internal events we do not clean up after execution. In the case of repeated call to urEnqueueKernelLaunch we eventually return UR_RESULT_ERROR_OUT_OF_RESOURCES. --------- Patch-by: Zhang, Winston <[email protected]>
When using internal events we do not clean up after execution. In the case of repeated call to urEnqueueKernelLaunch we eventually return UR_RESULT_ERROR_OUT_OF_RESOURCES.