Add nonblocking semantics to quilt spec #85
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 addresses issue #59.
Review from @kalzoo would be appreciated.
From what I could gather, the semantics of the non-blocking modifier is to not exclude the modified operation from simultaneous scheduling with operations on intersecting frames. But operations that are not non-blocking still exclude operations on intersecting frames in their usual way, including those frames marked as non-blocking.
I include @braised-babbage 's example in the spec to clarify that to make use of
NONBLOCKINGrequires modifying each operation meant to be mutually non-blocking.