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

Jump to bottom

Allow pset names to guide splitting in MPI_Comm_split_type #538

Closed
GuillaumeMercier opened this issue Feb 10, 2022 · 6 comments
Closed

Allow pset names to guide splitting in MPI_Comm_split_type #538

GuillaumeMercier opened this issue Feb 10, 2022 · 6 comments
Assignees
@GuillaumeMercier
Labels
chap-contexts Groups, Contexts, Communicators, Caching Chapter Committee had reading Completed the formal proposal reading mpi-4.1 For inclusion in the MPI 4.1 standard passed final vote Passed the final formal vote passed first vote Passed the first formal vote wg-hardware-topologies Hardware Topologies Working Group
Projects
MPI 4.1
Milestone
March 2023

Comments

@GuillaumeMercier
Copy link

GuillaumeMercier commented Feb 10, 2022 •
edited

Problem

Expand the possiblities of MPI_Comm_split_type by allowing the splitting to be guided by a process set name.
Since pset names can designate a hadware resource, this creates a bridge between two parts of the standard
that address the issue of hardware topologies management.

Proposal

Introduce a new split_type value (MPI_COMM_TYPE_RESOURCE_GUIDED) along with a new info keyval
(mpi_pset_name). This new split_type value also accepts the mpi_hw_resource_type) info key.
The goal would be to eventually deprecate MPI_COMM_TYPE_HW_GUIDED so that a single mechanism
is used to perform guided split.

Changes to the Text

Impact on Implementations

The new split type value duplicates the behavior of the already existing MPI_COMM_TYPE_HW_GUIDED
but the support for a new info key has to be added in implementations.

Impact on Users

Users would gain new ways to split communicators according to a specific criterion.

References and Pull Requests

See PR /mpi-forum/mpi-standard/pull/650
@GuillaumeMercier GuillaumeMercier mentioned this issue Feb 10, 2022
Open
@GuillaumeMercier GuillaumeMercier added chap-contexts Groups, Contexts, Communicators, Caching Chapter Committee wg-hardware-topologies Hardware Topologies Working Group labels Feb 10, 2022
@wesbland wesbland added this to To Do in MPI 4.1 via automation Mar 30, 2022
@wesbland
Copy link
Member

@GuillaumeMercier I'm assuming that you're targeting MPI 4.1 for this one. If you think it should go to 5.0, can you change the project please?

@GuillaumeMercier
Copy link
Author

@wesbland: Ok, thanks. 4.1 is the right target.

@wesbland wesbland added the mpi-4.1 For inclusion in the MPI 4.1 standard label Oct 19, 2022
@wesbland wesbland added the scheduled reading Reading is scheduled for the next meeting label Nov 21, 2022
@wesbland wesbland added this to the December 2022 milestone Nov 21, 2022
@wesbland wesbland added the had reading Completed the formal proposal reading label Dec 7, 2022
@wesbland
Copy link
Member

wesbland commented Dec 7, 2022

This had a reading on 2022-12-07.

@GuillaumeMercier GuillaumeMercier added the no-no Requires a no-no vote label Dec 8, 2022
@wesbland wesbland modified the milestones: December 2022, February 2023 Jan 17, 2023
@wesbland
Copy link
Member

wesbland commented Feb 1, 2023

This passed a no-no vote on 2023-02-01.

Yes No Abstain
30 0 1

@wesbland wesbland removed the no-no Requires a no-no vote label Feb 1, 2023
@wesbland
Copy link
Member

wesbland commented Feb 8, 2023

This passed a first vote on 2023-02-08.

Yes No Abstain
27 0 4

@wesbland wesbland added the passed first vote Passed the first formal vote label Feb 8, 2023
@wesbland wesbland removed the scheduled reading Reading is scheduled for the next meeting label Mar 1, 2023
@wesbland wesbland modified the milestones: February 2023, March 2023 Mar 1, 2023
@mpiforumbot
Copy link

This passed a 2nd vote.

Yes No Abstain
30 0 1

@mpiforumbot mpiforumbot added passed final vote Passed the final formal vote and removed scheduled vote labels Mar 21, 2023
@wgropp wgropp closed this as completed Mar 21, 2023
@hzhou hzhou mentioned this issue Nov 3, 2023
Closed
@hppritcha hppritcha mentioned this issue Nov 15, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GuillaumeMercier GuillaumeMercier

Labels
chap-contexts Groups, Contexts, Communicators, Caching Chapter Committee had reading Completed the formal proposal reading mpi-4.1 For inclusion in the MPI 4.1 standard passed final vote Passed the final formal vote passed first vote Passed the first formal vote wg-hardware-topologies Hardware Topologies Working Group
Projects
No open projects
MPI 4.1
To Do
MPI 4.1
Status: Done
Milestone
March 2023
Development

No branches or pull requests
3 participants
@wesbland @GuillaumeMercier @mpiforumbot