Skip to content

Conversation

@devreal
Copy link
Contributor

@devreal devreal commented Aug 13, 2021

So far Open MPI has elected to not hand out values for keys that were modified through MPI_*_set_info.
MPI 4.0 requires implementations to reflect such changes in MPI_*_get_info if the the new values are supported by the implementation. Hence, it is sufficient to simply duplicate the info object and remove the handling of OPAL_INFO_SAVE_PREFIX from OPAL entirely as there are no other users for this mechanism.

Fixes #9207
Closes #8505

Signed-off-by: Joseph Schuchart [email protected]

So far Open MPI has elected to not hand out values for keys
that were modified through MPI_*_set_info.
MPI 4.0 requires implementations to reflect such changes if the
the new values are supported by the implementation.
Hence, it is sufficient to simply duplicate the info object and
remove the handling of OPAL_INFO_SAVE_PREFIX from OPAL as there
are no other users of this infrastructure.
Signed-off-by: Joseph Schuchart <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MPI_Comm_set/get_info and relatives - need to check for MPI 4.0 compliance Changing info value on objects (should we remove __IN_ key prefixes?)

3 participants