Skip to content

Event should provide an inverse lookup to its origin Device/Context #491

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

Closed
leofang opened this issue Mar 5, 2025 · 0 comments · Fixed by #618
Closed

Event should provide an inverse lookup to its origin Device/Context #491

leofang opened this issue Mar 5, 2025 · 0 comments · Fixed by #618
Assignees
Labels
cuda.core Everything related to the cuda.core module enhancement Any code-related improvements P1 Medium priority - Should do

Comments

@leofang
Copy link
Member

leofang commented Mar 5, 2025

Follow-up of #487. Like CUDA streams, events today are also tied to a CUDA context, so it makes sense to offer the reverse link when an Event is created. This is particularly useful for bookkeeping, since unlike CUDA streams there is no driver/runtime API for querying the associated context.

@leofang leofang added cuda.core Everything related to the cuda.core module enhancement Any code-related improvements P1 Medium priority - Should do labels Mar 5, 2025
@leofang leofang added this to the cuda.core beta 4 milestone Mar 5, 2025
@leofang leofang added triage Needs the team's attention and removed triage Needs the team's attention labels Mar 5, 2025
@leofang leofang added P2 Low priority - Nice to have and removed triage Needs the team's attention P2 Low priority - Nice to have labels Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cuda.core Everything related to the cuda.core module enhancement Any code-related improvements P1 Medium priority - Should do
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants