Fune-tune the Ordering for all the atomics#447
Open
wang384670111 wants to merge 1 commit into
Open
Conversation
|
This looks good to me, but the maintainer @volcano0dr were too busy to review this PR |
|
Loom could be used to test the atomic orderings |
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
3 participants
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.
With the help of the static detector I wrote and my long-term research understanding of atomic:ordering, I made fine-grained modifications to the use of atomic::order in the teaclave source code and added relevant comments to address thread performance and security issues caused by sorting in specific processors.