Enclave connections and enclave coordination #44
Merged
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
even with a single worker, events might be scheduled asynchronously
unlock the mutex before trying to schedule an empty upstream event, which requires holding the upstream mutex.
cmnrd
changed the title
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.
This adds 3 new connection types
EnclaveConnection,DelayedEnclaveConnection, andPhysicalEnclaveConnectionthat facilitate the communication between scheduling enclaves. Additionally, this implements a coordination mechanism that allows individual enclaves to decide when it is safe to advance their logical time. For this, this PR introduces time barriers. They support a protocol where one party may try to acquire a tag and another party can release the tag. An acquire operation blocks until a tag greater or equal to the acquired one was released. This same mechanism can also be utilized for physical actions (here the physical clock continuously releases). Hence the mechanism implemented here unifies physical actions and inputs received from other enclaves (or later federates).