Skip to content

osc/rdma: use correct endpoint for local state #1319

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

Merged
merged 1 commit into from
Jan 22, 2016

Conversation

hjelmn
Copy link
Member

@hjelmn hjelmn commented Jan 22, 2016

If atomics are not globally visible (cpu and nic atomics do not mix)
then a btl endpoint must be used to access local ranks. To avoid
issues that are caused by having the same region registered with
multiple handles osc/rdma was updated to always use the handle for
rank 0. There was a bug in the update that caused osc/rdma to continue
using the local endpoint for accessing the state even though the
pointer/handle are not valid for that endpoint. This commit fixes the
bug.

Fixes #1241.

Signed-off-by: Nathan Hjelm [email protected]

If atomics are not globally visible (cpu and nic atomics do not mix)
then a btl endpoint must be used to access local ranks. To avoid
issues that are caused by having the same region registered with
multiple handles osc/rdma was updated to always use the handle for
rank 0. There was a bug in the update that caused osc/rdma to continue
using the local endpoint for accessing the state even though the
pointer/handle are not valid for that endpoint. This commit fixes the
bug.

Fixes open-mpi#1241.

Signed-off-by: Nathan Hjelm <[email protected]>
@hjelmn
Copy link
Member Author

hjelmn commented Jan 22, 2016

@sjeaugey Thanks for reporting this. I can no longer reproduce this issue with this fix.

hjelmn added a commit that referenced this pull request Jan 22, 2016
osc/rdma: use correct endpoint for local state
@hjelmn hjelmn merged commit 70787d1 into open-mpi:master Jan 22, 2016
@sjeaugey
Copy link
Member

All IB completion errors are gone. 👍

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.

Atomics get completion with error on mlx5
2 participants