[mpich-discuss] MPI_Comm_spawn info argument

[Matthieu Dorier]

Thanks Pavan and Wesley for your answers. 

Matthieu 

----- Mail original -----

> De: "Wesley Bland" <wbland at mcs.anl.gov>
> À: discuss at mpich.org
> Envoyé: Vendredi 2 Août 2013 17:27:44
> Objet: Re: [mpich-discuss] MPI_Comm_spawn info argument

> To answer your second question since Pavan covered #1, once the
> parent application spawns the child process(es), it gets back a new
> communicator called an intercommunicator. You can do communication
> on that communicator similarly to a normal communicator including an
> MPI_BARRIER. So when your child is done, you can call a barrier on
> both ends and be sure that you're done.

> Wesley

> On Friday, August 2, 2013 at 4:03 PM, Matthieu Dorier wrote:
> > Hi,
> 

> > Using MPI_Comm_spawn I'd like to know how to specify the list of
> > hosts on which to spawn the new processes. The standard
> > http://www.mpi-forum.org/docs/mpi-3.0/mpi30-report.pdf ) says that
> > the info field have some reserved keys, but nothing to actually
> > give
> > the list of hostnames. The closest key is "host" but it seems to
> > designate a single host, not a set, and not even the number of
> > process per host.
> 

> > What would be the keys for that in mpich and would they be
> > understood
> > my other implementation (e.g. OpenMPI)?
> 

> > Also another question related to MPI_Comm_spawn: how can a parent
> > application be aware that the application it spawned terminated?
> 
> > And what happens when the parent application exits before the
> > spawned
> > one?
> 

> > Thanks,
> 

> > Matthieu Dorier
> 
> > PhD student at ENS Cachan Brittany and IRISA
> 
> > http://people.irisa.fr/Matthieu.Dorier
> 

> > _______________________________________________
> 
> > discuss mailing list discuss at mpich.org
> 
> > To manage subscription options or unsubscribe:
> 
> > https://lists.mpich.org/mailman/listinfo/discuss
> 
> _______________________________________________
> discuss mailing list discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20130803/9fb3dfb4/attachment.html>