Skip to content
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

RequestTagMulti should expose CUDA stream or synchronize device #112

Open
pentschev opened this issue Oct 30, 2023 · 0 comments
Open

RequestTagMulti should expose CUDA stream or synchronize device #112

pentschev opened this issue Oct 30, 2023 · 0 comments

Comments

@pentschev
Copy link
Member

pentschev commented Oct 30, 2023

Currently RequestTagMulti doesn't take into consideration CUDA synchronization which is an error. The user should be able to consume any received data or release any sent data immediately after the request completes, without having to care about synchronization. Another valid approach would be to let the user specify a CUDA async stream, and in that case release the synchronization requirement back to the user.

When this is fixed, remove

# TODO: We don't know if any frames are CUDA, investigate whether
# we need to synchronize device here.

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

No branches or pull requests

1 participant