Skip to content

Conversation

bosilca
Copy link
Member

@bosilca bosilca commented Dec 11, 2019

This is a replacement for @hjelmn #7063.

hjelmn and others added 2 commits October 8, 2019 21:10
This commit updates the coll/basic component to correctly order sends
and receives for cartesian communicators with cyclic boundaries. This
addresses an issue identified by mpi-forum/mpi-issues#153. This issue
occurs when the size in any dimension is 1. This gives the same
neighbor in the positive and negative directions. The old code was
sending and receiving in the same order so the -1 buffer contained
the +1 result and vise-versa. The problem is addressed by using
unique tags for each send. This should cover both the case where
overtaking is allowed and is not allowed. The former case will be
possible is a MPI_Cart_create_with_info() call is added to the
standard.

Signed-off-by: Nathan Hjelm <hjelmn@google.com>
This work is rooted in the [MPI Forum issue
153](mpi-forum/mpi-issues#153).

Signed-off-by: George Bosilca <bosilca@icl.utk.edu>
@jsquyres
Copy link
Member

bot:ompi:retest

@bosilca bosilca requested a review from hjelmn December 11, 2019 20:32
@jsquyres
Copy link
Member

@hppritcha @bwbarrett Any idea how this PR is failing CI in configure when @bosilca didn't touch any configury in this PR?

@hppritcha
Copy link
Member

bot:ompi:retest

@jsquyres
Copy link
Member

@bosilca @hjelmn Is there anything else to do on this PR, or is mpi-forum/mpi-issues#153 now fully fixed?

@bosilca
Copy link
Member Author

bosilca commented Dec 17, 2019

We are now fully MPI compliant, at least from the neighbor collective point of view. As for what is left to be done: we need to push this into the stable branches.

@jsquyres jsquyres merged commit 8b424c3 into open-mpi:master Dec 17, 2019
@bosilca bosilca deleted the hjelmn_neighbor_alltoall_fix branch February 29, 2020 15:49
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.

4 participants