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.

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

synchronization: guarantee that a ULT does not yield if no contention #287

Closed
shintaro-iwasaki opened this issue Jan 6, 2021 · 1 comment · Fixed by #288
Closed

synchronization: guarantee that a ULT does not yield if no contention #287

shintaro-iwasaki opened this issue Jan 6, 2021 · 1 comment · Fixed by #288

Comments

@shintaro-iwasaki
Copy link
Collaborator

This issue is raised by @carns. https://lists.argobots.org/pipermail/discuss/2021-January/000094.html

We need to examine the implementation, but in any case the Argobots specification should guarantee that a ULT that locks/unlocks asynchronization object may not spuriously yield if there is no contention (e.g., mutex) and otherwise explicitly stated. At least I implemented so as a developer, but this behavior should be clarified and tested. Maybe there are some bugs.

@carns
Copy link
Contributor

carns commented Jan 7, 2021

Just to follow up on the github issue: the only instance I have observed where this guarantee does not hold is on a power9 CPU with Argobots 1.0. It works as expected now with origin/main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants