Achieve lock-freeness #9
Open
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
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.
TODO: There is still the possibility of a lock when a write bit/block is claimed but the thread falls dormant before writing to it. All readers will continuously try to read from this block without being able to move the window.
The remedy seems to be giving the pop operation the responsibility of resolving spurious block claims / empty blocks in general.
It's important to note that this necessitates sealing the block (by increasing its epoch).
Originally it was thought that only the push operation CAN resolve spurious block claims, but this assumption seems to be false if we simply seal the block instead of solely resetting the bit.
Did I simply fail to consider this or am I missing something now?