Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Non-blocking atomic fetch is not non-blocking #1066

Open
wrrobin opened this issue Sep 30, 2022 · 0 comments
Open

Non-blocking atomic fetch is not non-blocking #1066

wrrobin opened this issue Sep 30, 2022 · 0 comments

Comments

@wrrobin
Copy link
Collaborator

wrrobin commented Sep 30, 2022

Non-blocking atomic fetch uses fi_fetch_atomic with DELIVERY_COMPLETE flag. This ensures that the value is fetched before returning. Should it use the FI_INJECT without any completion semantics?

Also, for the same reason, does the blocking atomic fetch require a call to get_wait?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wrrobin