We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Dan reviews chapter 10 since we didn't get to that at the F2F Forum in Chicago in May.
Question about dynamic process model. Should we change this name? No. that's the consensus.
Do we need to return to MPI_INFO_ENV sentence about may also be queried following.... Marc Andres' ticket for info objects will impact this.
MPI_INFO_ENV
may also be queried following...
Should we add a caveat/info to users for MPI_THREAD_SINGLE when initializing a session.
MPI_THREAD_SINGLE
text around MPI_Session_finalize including the process. Maybe add references to MPI_XXX_FREE?
MPI_Session_finalize
process
MPI_XXX_FREE
process sets - modify per Ryan's info changes (buffer length in C).
10.4.1 - maybe don't call it an MPI process since its not initialized yet. Add MPI before finalization.
remove dup double in table in 10.4.1
add query thread etc. to the ```MPI_IS_THREAD_MAIN`` to the table and add list in 10.6 reference.
add a bit more about number of psets that can be returned from MPI_Get_num_psets. Something about never go down.
MPI_Get_num_psets
MPI_Abort
The text was updated successfully, but these errors were encountered:
No branches or pull requests
capture feedback from virtual form
Dan reviews chapter 10 since we didn't get to that at the F2F Forum in Chicago in May.
Question about dynamic process model. Should we change this name? No. that's the consensus.
Do we need to return to
MPI_INFO_ENV
sentence aboutmay also be queried following...
. Marc Andres' ticket for info objects will impact this.Should we add a caveat/info to users for
MPI_THREAD_SINGLE
when initializing a session.text around
MPI_Session_finalize
including theprocess
. Maybe add references toMPI_XXX_FREE
?process sets - modify per Ryan's info changes (buffer length in C).
10.4.1 - maybe don't call it an MPI process since its not initialized yet. Add MPI before finalization.
remove dup double in table in 10.4.1
add query thread etc. to the ```MPI_IS_THREAD_MAIN`` to the table and add list in 10.6 reference.
add a bit more about number of psets that can be returned from
MPI_Get_num_psets
. Something about never go down.punt to other WGs
MPI_Abort
definition. (Punt this to fault tolerance working groupThe text was updated successfully, but these errors were encountered: