[cuda] Optimize device signal to host wait synchronization #14876
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When we have a device `CUevent` signaling past a desired timepoint waited by the host, we can actually wait on the `CUevent` using `cuEventSynchronize`. This is profiled to be quite faster than waiting on the full flow of device singal -> cuLaunchHostFunc (async) -> host signal -> host polling.
ezhulenev
approved these changes
Aug 30, 2023
ScottTodd
reviewed
Aug 30, 2023
ScottTodd
approved these changes
Aug 31, 2023
jinchen62
pushed a commit
to jinchen62/iree
that referenced
this pull request
Sep 18, 2023
…14876) When we have a device `CUevent` signaling past a desired timepoint waited by the host, we can actually wait on the `CUevent` using `cuEventSynchronize`. This is profiled to be quite faster than waiting on the full flow of device singal -> cuLaunchHostFunc (async) -> host signal -> host polling.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we have a device
CUeventsignaling past a desired timepoint waited by the host, we can actually wait on theCUeventusingcuEventSynchronize. This is profiled to be quite faster than waiting on the full flow of device singal -> cuLaunchHostFunc (async) -> host signal -> host polling.