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.
Yes, it's right!
Now i can see btl_tcp_if_include flag:
MCA btl: parameter "btl_tcp_if_include" (current value: <none>, data source:
MCA btl: parameter "btl_tcp_if_exclude" (current value: "eth0,ib0,ib1", data
My actual configuration is:
btl = ^tcp
btl_tcp_if_exclude = eth0,ib0,ib1
oob_tcp_include = eth1,lo
But is it right? I have some doubt..
2010/4/13 Jeff Squyres <jsquyres_at_[hidden]>
> On Apr 13, 2010, at 9:03 AM, Gabriele Fatigati wrote:
> > ompi_info --param btl tcp
> Ah ha... this is revealing:
> > MCA btl: parameter "btl" (current value: "^tcp", data
> source: file
> > Default selection set of components for the btl
> framework (<none> means use all components that can be found)
> It seems you have a config file
> that is excluding the TCP BTL from being used.
> This config file will even prevent the TCP BTL from being shown in
> ompi_info -- remember that ompi_info shows *current* values of MCA
> parameters. So you might want to do something like this:
> ompi_info --mca btl "" --param btl tcp
> That would override the "btl" MCA parameter in your config file, allow the
> BTL TCP to be loaded by ompi_info, and therefore show you all the BTL TCP
> Make sense?
> Jeff Squyres
> For corporate legal information go to:
> users mailing list
Ing. Gabriele Fatigati
CINECA Systems & Tecnologies Department
Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy
www.cineca.it Tel: +39 051 6171722
g.fatigati [AT] cineca.it