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

MPI_Comm_split_type with MPI_COMM_TYPE_HW_GUIDED seems inconsistent #7160

Open
th-hlrs opened this issue Oct 4, 2024 · 0 comments
Open

MPI_Comm_split_type with MPI_COMM_TYPE_HW_GUIDED seems inconsistent #7160

th-hlrs opened this issue Oct 4, 2024 · 0 comments

Comments

@th-hlrs
Copy link

th-hlrs commented Oct 4, 2024

The current implementation leads to the (in my opinion) weird behavior that using MPI_Comm_split_type with MPI_COMM_TYPE_HW_GUIDED

  • and setting the `info` to `mpi_hw_resource_type = mpi_shared_memory` one gets a valid new communicator
    
  • while setting the `info` to `mpi_hw_resource_type = Package` leads to `MPI_COMM_NULL` on a system with only one package (since there is no proper subset) and the `if` statement at https://github.com/pmodels/mpich/blob/b53cc3fb5bb36aac7c244ba6d65ee2fdf3df8a44/src/mpi/comm/comm_split_type.c#L180C5-L180C7
    

At least that is how I read the code and what my experiments showed (on a server and my laptop).

My understanding of the MPI standard is that for MPI_COMM_TYPE_HW_GUIDED no proper subset is required

The MPI implementation will return in the group of the output communicator newcomm the largest subset of MPI processes that match the splitting criterion.

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

No branches or pull requests

1 participant