Introduce foundation for broadcast channel #633
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR introduces a
broadcastchannel allocation method tocommunication::Allocate. It defaults to using a point-to-point channel and cloning the contents, but it can be implemented more thoughtfully by implementors. For example, we might soon like to have the inter-process channels only send the data once, rather than once for each remote worker.Potential follow-up: an
all_reducechannel, not unlike a broadcast channel but with the opportunity to consolidate updates that move along the channel. Both the broadcast and hypothetical all-reduce are in service of progress messages, which support an all-reduce pattern.