Just to make sure I"m not losing it - if any of the "high speed"
networks is found between peers, tcp shouldn't be used between that
pair, right? I was pretty sure that's what the priority code did
now, but wanted to make sure I wasn't losing it ;).
Begin forwarded message:
> From: "Tim S. Woodall" <twoodall_at_[hidden]>
> Date: September 20, 2005 7:51:42 PM GMT+02:00
> To: Open MPI Users <users_at_[hidden]>
> Subject: Re: [O-MPI users] HOWTO turn of "multi-rail" support at
> Reply-To: Open MPI Users <users_at_[hidden]>
> Try setting:
> -mca btl_base_include self,mvapi
> To specify that only lookback (self) and mvapi btls should be used.
> Can you forward me the config.log from your build?
> Daryl W. Grunau wrote:
>> Hi, I've got a dual-homed IB + GigE connected cluster for which
>> I've built
>> a very recent drop of OpenMPI (w/ mvapi support). I'm having
>> making OMPI solely use native verbs as it's communication between
>> I've tried all incantations of the following mca parameters to no
>> --mca btl_tcp_if_exclude "lo,eth0,eth1,ib0,ib1"
>> --mca ptl_tcp_if_include "lo,eth0,eth1,ib0,ib1"
>> Note I'm putting ib in the list because I really don't wish to use
>> OMPI should be able to communicate at the native verbs level,
>> right? If I
>> leave ib0/1 unconfigured on my host, OMPI uses eth0 for its
>> If I bring up ib0, OMPI uses both eth0 and ib0! Is there any way
>> I can
>> specify for it to use none of these TCP interfaces? TIA!
>> P.s. I can send output of ompi_info if that is helpful.
>> users mailing list
> users mailing list