Issue 414: ordering & method of specifying procs in collectives clarified #490
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dsolt
changed the title
… clarified Signed-off-by: David Solt <dsolt@us.ibm.com>
dsolt
force-pushed
the
issue_414_process_description_ordering
branch
from
8cd63be
to
dff11f0
Compare
|
PMIx ASC 4Q 2023 Meeting
|
dsolt
commented
Oct 30, 2023
| The ordering of the entries in the \refarg{procs} has no significance, neither is the method used for identifying processes. | ||
| Some callers may describe the target set of processes using PMIX_RANK_WILDCARD while other | ||
| callers may list the individual processes of a namespace explicitly. | ||
|
|
||
| If the \refattr{PMIX_GROUP_NOTIFY_TERMINATION} attribute is provided and has a value of \code{true}, then either the construct leader (if \refattr{PMIX_GROUP_LEADER} is provided) or all participants who register for the \refconst{PMIX_GROUP_MEMBER_FAILED} event will receive events whenever a process fails or terminates prior to calling \refapi{PMIx_Group_construct} – i.e. if a \emph{group leader} is declared, \textit{only} that process will receive the event. In the absence of a declared leader, \textit{all} specified group members will receive the event. |
There was a problem hiding this comment.
Add a brief comment that "Because the name is used to determine the uniqueness of the collective...."
…y than PMIx_Connect (req. during 23Q4)
abouteiller
added
the
Accepted as Provisional
|
PMIx ASC 2024Q1 Meeting Passed first vote: 9 yes / 0 no / 0 abstain |
abouteiller
approved these changes
Feb 28, 2024
|
@pmix/asc-release-managers ready to merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… clarified
Signed-off-by: David Solt dsolt@us.ibm.com