The original MPI sessions proposal intended for the MPI_Session_init method to be local and lightweight. MPI processes are permitted to make any number of calls to this method without any coordination with other MPI processes.
However, there is not an explicit mention of this in the text block describing MPI_Session_init (currently section 11.3.1).
The only explicit mention of this is in the table in Appendix A, section 2.
Proposal
Add a sentence in the text block describing MPI_Session_init that it is a local operation.
Changes to the Text
TBD in a PR.
Impact on Implementations
If implementations currently implement MPI_Session_init in a way that requires activity by other MPI processes to complete, then implementation will need to be refactored.
Impact on Users
No impact on users provided they are not assuming MPI_Session_init is in some way synchronizing.
Problem
The original MPI sessions proposal intended for the MPI_Session_init method to be local and lightweight. MPI processes are permitted to make any number of calls to this method without any coordination with other MPI processes.
However, there is not an explicit mention of this in the text block describing MPI_Session_init (currently section 11.3.1). The only explicit mention of this is in the table in Appendix A, section 2.
Proposal
Add a sentence in the text block describing MPI_Session_init that it is a local operation.
Changes to the Text
TBD in a PR.
Impact on Implementations
If implementations currently implement MPI_Session_init in a way that requires activity by other MPI processes to complete, then implementation will need to be refactored.
Impact on Users
No impact on users provided they are not assuming MPI_Session_init is in some way synchronizing.
References and Pull Requests
TBD