[Mpi-forum] Communicator info arguments

Jeff Hammond jhammond at alcf.anl.gov
Fri Dec 7 16:01:24 CST 2012

>From MPI-3 6.4.2 (MPI_COMM_DUP):

"MPI_COMM_DUP duplicates the existing communicator comm with the
associated key values, topology information and info hints."

"MPI_COMM_DUP_WITH_INFO behaves exactly as MPI_COMM_DUP except that
the info hints associated with the communicator comm are not
duplicated in newcomm.  The hints provided by the arguments info are
associated with the output communicator newcomm instead."


On Fri, Dec 7, 2012 at 3:56 PM, Pavan Balaji <balaji at mcs.anl.gov> wrote:
> Apologies if this query needs to go a specific working group.  I wasn't
> sure which one, so I'm sending it to the overall mailing list.
> If a communicator is created using MPI_COMM_DUP_WITH_INFO, is the info
> argument "sticky" to all child communicators?  That is, if I split the
> output communicator further, will the info argument propagate?
> Adam said that it would, at the Forum, but that doesn't seem accurate,
> since that'll get weird if I do an Intercomm_merge with two
> communicators, one of which has an info argument and the second does not.
> I couldn't find text saying one way or another in the document.
>  -- Pavan
> --
> Pavan Balaji
> http://www.mcs.anl.gov/~balaji
> _______________________________________________
> mpi-forum mailing list
> mpi-forum at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

Jeff Hammond
Argonne Leadership Computing Facility
University of Chicago Computation Institute
jhammond at alcf.anl.gov / (630) 252-5381

More information about the mpi-forum mailing list