Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Using OPENMPI configured for MX, GM and OPENIB interconnects
From: twurgl_at_[hidden]
Date: 2009-08-26 16:20:17

I see. My one script for all clusters calls

mpirun --mca btl openib,mx,gm,tcp,sm,self ....

so I'd need to add some logic above the mpirun line to figure out what
cluster I am on to setup the correct mpirun line.

still seems like I should be able to do the mpirun line I have and just
tell me what it found, not what it can't find.

thanks for the workaround...


             Scott Atchley
> To
             Sent by: Open MPI Users <users_at_[hidden]>
             users-bounces_at_ope cc
                                       Re: [OMPI users] Using OPENMPI
             08/26/2009 03:57 configured for MX, GM and OPENIB
             PM interconnects
             Please respond to
              Open MPI Users

On Aug 26, 2009, at 3:41 PM, twurgl_at_[hidden] wrote:

> When, for example, I run on an IB cluster, I get warning messages
> about not
> finding GM NICS and another transport will be used etc.
> And warnings about mca btl mx components not found etc. It DOES run
> the
> IB, but it never says that in the output.
> What I'd like is to not get warnings about what I don't have on the
> cluster
> in question and instead get a note that says it found the IB.
> Is this already possible?
> Or can I at least suppress the warnings for the not-found
> interconnects?
> thanks!
> tom

You can use:

$ mpirun -mca pml ob1 -mca mx,sm,self ...

when running with MX. Substitute gm or ib when running on those

It may still fail over to TCP. To avoid that, you could run:

$ mpirun -mca pml ob1 -mca ^mx,^ib,^tcp ...

to tell it to run on anything (GM, shared memory and self) except MX,
IB, and TCP.

You probably do not need -mca pml ob1, but that will prevent the MX
MTL from trying to start as well.

users mailing list