This ticket relaxes the restriction that info keys cannot change semantics. It allows info keys to be used to provide application behavior hints, which an implementation can use to restrict the set of functionality or semantics supported, e.g. on a particular communicator, to optimize performance for the given usage model.
This proposal also removes info key propagation from MPI_COMM_DUP to ensure backward compatibility with existing applications and libraries. MPI_COMM_DUP_WITH_INFO should be used to explicitly propagate info hints.
Originally by jdinan on 2015-05-04 11:19:47 -0500
Summary
This ticket relaxes the restriction that info keys cannot change semantics. It allows info keys to be used to provide application behavior hints, which an implementation can use to restrict the set of functionality or semantics supported, e.g. on a particular communicator, to optimize performance for the given usage model.
This proposal also removes info key propagation from MPI_COMM_DUP to ensure backward compatibility with existing applications and libraries. MPI_COMM_DUP_WITH_INFO should be used to explicitly propagate info hints.
Proposed Changes
See attached proposal.
Related Tickets
381 -- Communicator info assertions