Option to disable non-fetch AMO #1131
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
philipmarshall21
approved these changes
Jun 5, 2024
davidozog
approved these changes
Jun 5, 2024
davidozog
pushed a commit
to davidozog/sandia-shmem
that referenced
this pull request
Oct 9, 2024
* Workaround for non-fetch AMO on CXI * Switching to fetch AMO * CI check for disable of non-fetch AMO
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 PR adds support to optionally disable non-fetch AMO and instead fetch AMO. This is due to a bug with non-fetch AMO on CXI provider that gets stuck after a certain number of operations when optimized MR mode is not used. This is a temporary work-around and may be removed as the original bug is resolved.