[mpich-discuss] How to spawn a non-MPI process with MPI_Comm_spawn
Raffenetti, Kenneth J.
raffenet at mcs.anl.gov
Mon Jan 13 13:18:22 CST 2020
I'm afraid I don't have a great answer for this. Hydra, the default
MPICH process manager, uses fork/execvp to launch (or spawn) MPI
processes. But this happens at the node-level daemon. As you noted, this
may not be safe to do from the MPI-level, particularly if using an RDMA
network. If MPICH is not configured for RDMA (i.e. TCP/IP), fork/exec
should be OK for creating non-MPI processes.
On 1/7/20 10:07 AM, Mccall, Kurt E. (MSFC-EV41) wrote:
> Issue created. Can you suggest any other way to launch non-MPI processes?
> -----Original Message-----
> From: Raffenetti, Kenneth J. <raffenet at mcs.anl.gov>
> Sent: Tuesday, January 7, 2020 9:32 AM
> To: discuss at mpich.org
> Cc: Mccall, Kurt E. (MSFC-EV41) <kurt.e.mccall at nasa.gov>
> Subject: [EXTERNAL] Re: [mpich-discuss] How to spawn a non-MPI process with MPI_Comm_spawn
> We do not support such a key at this time, but it seems reasonable to add. Could you create an issue on our GitHub?
> On 1/6/20 9:50 AM, Mccall, Kurt E. (MSFC-EV41) via discuss wrote:
>> I'm attempting to use MPICH to manage a number of non-MPI processes.
>> The latter call system() and fork(), which as I understand it may
>> cause undefined behavior if they were spawned as MPI processes. How
>> do I use
>> MPI_Comm_spawn() to launch these processes?
>> For example, OpenMpi has a key for the "info" field named
>> "ompi_non_mpi", which causes a non-MPI process to be spawned. Is
>> there something similar in MPICH?
>> discuss mailing list discuss at mpich.org
>> To manage subscription options or unsubscribe:
More information about the discuss