[mpich-discuss] Force MPICH2 to not use network adapter

Balaji, Pavan balaji at anl.gov
Thu Nov 6 23:50:01 CST 2014


Igor,

Based on the fact that you are asking about smpd and -localonly options, I’m assuming you are using a super-ancient vesion of MPICH that dinosaurs used to compute with.  Perhaps you can upgrade to the latest version?  For the past 10 years or so, we have been automatically detecting shared memory and using it internally without going over the network.

  — Pavan

> On Nov 6, 2014, at 8:28 PM, Igor Raskin <igor.raskin at weblakes.com> wrote:
> 
> Hello,
>  
> I am running a multi-process calculations using MPICH2 from Argonne National Laboratory. The run is on a single machine, so -localonly option of mpiexec is used. Usually everything works.
> If the network adapter is enabled when the run starts, and if I disable it during the run, the run fails with error stating:
> 
> op_read error on left context: Error = -1
>  
> op_read error on parent context: Error = -1
>  
> unable to read the cmd header on the left context, Error = -1
> .
> unable to read the cmd header on the parent context, Error = -1
> .
> Error posting readv, An existing connection was forcibly closed by the remote host.(10054)
> connection to my parent broken, aborting.
> state machine failed.
> However, if the network adapter is disabled when the run is started, I can enable/disable the adapter as many times as I want, and the run still proceeds to the end.
> 
> Is there a way to run mpiexec or modify smpd configuration such that MPICH2 is not using network adapter for inter-process communication for local runs even if the adapter is available when the run starts?
>  
> Thank you,
>  
> Igor
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss

--
Pavan Balaji  ✉️
http://www.mcs.anl.gov/~balaji



More information about the discuss mailing list