[XLA] Allow synchronously invoking computations on separate threads #22441
+28
−14
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
test_724086062
branch
5 times, most recently
from
1606e5e to
f97d893
Compare
If we allow asynchronously invoking a computation on a separate thread by wrapping the kCall op in a async-{start,done} pair, then we should also allow a synchronous version of kCall to do the same. Same logic applies kCustomCall.
PiperOrigin-RevId: 724489268
copybara-service
bot
force-pushed
the
test_724086062
branch
from
f97d893 to
5bf21f2
Compare
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.
[XLA] Allow synchronously invoking computations on separate threads
If we allow asynchronously invoking a computation on a separate thread by wrapping the kCall op in a async-{start,done} pair, then we should also allow a synchronous version of kCall to do the same. Same logic applies kCustomCall.