Skip to content

Conversation

gmlueck
Copy link
Contributor

@gmlueck gmlueck commented Oct 7, 2025

Add a proposed extension specification which allows an application to reuse the same event object in multiple command submissions, rather than creating a new event for each submission.

Add a proposed extension specification which allows an application to
reuse the same event object in multiple command submissions, rather than
creating a new event for each submission.
@gmlueck gmlueck requested a review from a team as a code owner October 7, 2025 21:43
@gmlueck
Copy link
Contributor Author

gmlueck commented Oct 7, 2025

This PR proposes a new extension that relies on changes in #20308. However, I think the two PRs can be approved and merged separately. Note that this PR (#20309) only proposes a new extension, so it's OK if this proposed extension is merged even before #20308 is implemented. It is only necessary that #20308 be implemented by the time the extension proposed in #20309 is implemented.

This extension adds the ability to reuse the same `event` object in multiple
command submissions, rather than creating a new event for each submission.
This pattern may perform better on some implementations because fewer event
objects need to be created and destroyed.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sergey-semenov are you familiar with the way events are managed in the DPC++ SYCL runtime? If so, I'd be interested in your thoughts on whether this proposed API would allow us to implement events more efficiently. I have an intuition that it will help, but I don't know how the code really works today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant