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

UCX osc: properly release exclusive lock to avoid lockup (v4.0.x) #6934

Merged
merged 1 commit into from
Aug 29, 2019

Conversation

devreal
Copy link
Contributor

@devreal devreal commented Aug 27, 2019

Cherry-pick of #6933 to v4.0.x

See #6931 for the issue this fixes.

Signed-off-by: Joseph Schuchart schuchart@hlrs.de
(cherry picked from commit 08cb638)

Signed-off-by: Joseph Schuchart <schuchart@hlrs.de>
(cherry picked from commit 08cb638)
@devreal devreal force-pushed the osc-ucx-excl-lock-v4.0.x branch from 06d1f4c to 8d130e1 Compare August 27, 2019 21:13
@gpaulsen gpaulsen requested a review from hoopoepg August 28, 2019 18:42
@gpaulsen
Copy link
Member

@hoopoepg Would you be able to review this code?

@gpaulsen gpaulsen merged commit 2d515f7 into open-mpi:v4.0.x Aug 29, 2019
@artpol84
Copy link
Contributor

@devreal @hoopoepg @brminich I see that this PR changes abstracted use of UCX to a direct call.
Is it absolutely necessary? I'd prefer to keep abstraction.

@artpol84
Copy link
Contributor

Ok, I confused this with master. It is OK for it to be this way in 4.0.x

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

Successfully merging this pull request may close these issues.

5 participants