It is anticipated that process set names will be used in more dynamic ways as the use cases for sessions broadens.
The wording around sessions and process set names in the process management chapter was intentionally made general enough that the methods defined in the chapter would not be overly restrictive on how process set names are generated and made usable by an MPI implementation.
In the Groups, communciators, etc. chapter there was wording about the pset_name argument to MPI_GROUP_FROM_SESSION_PSET that was restrictive in these regards. The Sessions WG wants to change the wording to relax this restriction.
Changes to the Text
Impact on Implementations
Would allow implementations to permit use of pset_names that the application acquired by means other than querying MPI_SESSION_GET_NTH_PSET.
Impact on Users
Allows users to obtain pset_names from, for example, the runtime using non-MPI methods.
Problem
It is anticipated that process set names will be used in more dynamic ways as the use cases for sessions broadens. The wording around sessions and process set names in the process management chapter was intentionally made general enough that the methods defined in the chapter would not be overly restrictive on how process set names are generated and made usable by an MPI implementation.
In the Groups, communciators, etc. chapter there was wording about the
pset_name
argument toMPI_GROUP_FROM_SESSION_PSET
that was restrictive in these regards. The Sessions WG wants to change the wording to relax this restriction.Changes to the Text
Impact on Implementations
Would allow implementations to permit use of
pset_names
that the application acquired by means other than queryingMPI_SESSION_GET_NTH_PSET
.Impact on Users
Allows users to obtain
pset_names
from, for example, the runtime using non-MPI methods.References and Pull Requests
https://github.com/mpi-forum/mpi-standard/pull/938