Persistent interface in Reconverse - #192
Merged
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 implements the full persistent API as described in the Converse documentation.
The Persistent API supports communication between any pair of PEs, either on the same process or on different processes. Communication between processes can be done with or without RMA/RDMA.
There are differences between the Reconverse implementation and the old Converse (no longer operative) implementation. These include allowing persistence between same-node PEs (done to keep the interface consistent and the code simple), and not implementing the undocumented "Compress" variants.
This requires the reconverse-persistent branch of charm++, which will be merged into reconverse-specific-build once this is merged.