-
Notifications
You must be signed in to change notification settings - Fork 758
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] Disable deferred buffer release for interop handle usage #11220
[SYCL] Disable deferred buffer release for interop handle usage #11220
Conversation
Signed-off-by: Tikhomirova, Kseniya <kseniya.tikhomirova@intel.com>
Failed Tests (1): is unrelated, reported here #11277 |
Failed Tests (1): Testing Time: 2738.61s |
failure is already reported here #11277 |
@cperkinsintel kindly ping |
enum PropertySupport { NotSupported = 0, Supported = 1, NotChecked = 2 }; | ||
|
||
private: | ||
bool MOwnedByRuntime; |
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.
I like this name much better than "KeepOwnership" which was always confusing to me. Kept by whom?
Thanks!
Since this is a test involving L0 ownership, shouldn't it have at least one E2E test? |
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, but I do have a question about whether an E2E test is needed.
there is no way to check if destructor was blocking or not in E2E test. I could check this mechanism only via unittests. |
@cperkinsintel are you ok to merge it? |
@cperkinsintel kindly ping |
I'm Ok to merge it |
non-blocking buffer destructor could not be used with L0 interop handles with ownership "keep" since no way to distinguish when all resources is released by RT.