[WIP] Use new Agrona release functions #1748
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
pveentjer
changed the title
These functions replace the Ordered functions.
pveentjer
force-pushed
the
improvement/use-agrona-release-functions
branch
from
140626d to
5643eab
Compare
pveentjer
changed the title
pveentjer
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.
These functions replace the Ordered functions. E.g. AtomicCounter.setLongOrdered is now AtomicCounter.setLongRelease. The release and ordered functions have exactly the same memory semantics.
Relies on Agrona 2.1.0.
This PR will not contain any relaxations of memory ordering behavior like the new opaque methods; it is purely switching from ordered to release methods.
In a follow up PR these relaxations can be implemented.