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

Create MPI_INFO_ENV before MPI_INIT #143

Closed
wesbland opened this issue Aug 19, 2019 · 9 comments
Closed

Create MPI_INFO_ENV before MPI_INIT #143

wesbland opened this issue Aug 19, 2019 · 9 comments
Assignees
Labels
had reading Completed the formal proposal reading passed final vote Passed the final formal vote passed first vote Passed the first formal vote scheduled reading Reading is scheduled for the next meeting wg-ft Fault Tolerance Working Group wg-sessions Sessions Working Group wg-tools Tools Working Group

Comments

@wesbland
Copy link
Member

wesbland commented Aug 19, 2019

Problem

As part of a number of proposals (improving error handling - #102, sessions - #103, and tools) it is helpful to have access to an MPI_INFO_ENV-like object before MPI_INIT is called. The ability to manipulate MPI_INFO objects before initialization is being proposed as part of Sessions (#103), but the ability to construct such an object is not part of that proposal.

Proposal

This proposes a new function called MPI_INFO_ENV_CREATE_ARGV which would allow the user to pass in the argc and argv parameters and receive an MPI_INFO_ENV-like object back, which could be used for all of the same functionality as MPI_INFO_ENV.

Changes to the Text

The new function MPI_INFO_ENV_CREATE_ARV is added and described.

Impact on Implementations

Implementations will need to implement the new function, which should hopefully be the same code as is currently used in MPI_INIT. It's possible that if the implementation relies on the input parameters to MPI_INIT for argc and argv and doesn't currently have another way of getting those values, the output info object here might not be the same as MPI_INFO_ENV.

Impact on Users

Users not using this function will not be impacted. Users who want to use this function for the purposes mentioned above will be able to access the MPI_INFO_ENV-like object before initialization.

References

The pull request is available at https://github.com/mpi-forum/mpi-standard/pull/126

@wesbland wesbland added mpi-4.0 scheduled reading Reading is scheduled for the next meeting wg-tools Tools Working Group wg-ft Fault Tolerance Working Group wg-sessions Sessions Working Group labels Aug 19, 2019
@wesbland wesbland added this to the 2019-09 Zurich, Switzerland milestone Aug 19, 2019
@wesbland wesbland self-assigned this Aug 19, 2019
@wesbland
Copy link
Member Author

wesbland commented Sep 6, 2019

PDF including no-no changes made on 2019-09-06: mpi40-report-get_info_env.pdf

@wesbland
Copy link
Member Author

wesbland commented Sep 6, 2019

PDF including no-no changes for 2019-09-07: mpi40-report-get_info_env.pdf

@ahori
Copy link

ahori commented Sep 7, 2019

I wonder why you did not mention that this routine can be called before calling MPI_INIT. Isn't this the point of this routine?

@wesbland
Copy link
Member Author

wesbland commented Sep 7, 2019

That's a good point. I'll fix that before the reading.

mpi40-report-get_info_env.pdf

@wesbland
Copy link
Member Author

wesbland commented Dec 9, 2019

This is the PDF to be read at the December 2019 meeting.

@wesbland
Copy link
Member Author

This commit, https://github.com/mpi-forum/mpi-standard/pull/126/commits/67b597098d3880d4fc282badcae0d051be5af72a, will be read as a no-no item at the December 2019 meeting.

@wesbland wesbland added the had reading Completed the formal proposal reading label Dec 12, 2019
@wesbland
Copy link
Member Author

This passed the no-no vote in Albuquerque, New Mexico on 2019-12-12.

@wesbland wesbland added the passed first vote Passed the first formal vote label Feb 21, 2020
@wesbland
Copy link
Member Author

This proposal passed a first vote at the February 2020 meeting:

Yes - 23
No - 0
Abstain - 1

@wesbland wesbland added the passed final vote Passed the final formal vote label Jul 11, 2020
@wesbland
Copy link
Member Author

This passed a second vote on 2020-06-30.

https://www.mpi-forum.org/meetings/2020/06/votes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
had reading Completed the formal proposal reading passed final vote Passed the final formal vote passed first vote Passed the first formal vote scheduled reading Reading is scheduled for the next meeting wg-ft Fault Tolerance Working Group wg-sessions Sessions Working Group wg-tools Tools Working Group
Projects
None yet
Development

No branches or pull requests

2 participants