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: default value) MCA btl: parameter "btl_tcp_if_exclude" (current value: "eth0,ib0,ib1", data source: file [/cineca/prod/opt/compilers/openmpi/1.3.3/intel--11.1--binary/etc/openmpi-mca-params.conf]) 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 <jsquy...@cisco.com> > 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 > > > [/cineca/prod/opt/compilers/openmpi/1.3.3/intel--11.1--binary/etc/openmpi-mca-params.conf]) > > 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 > /cineca/prod/opt/compilers/openmpi/1.3.3/intel--11.1--binary/etc/openmpi-mca-params.conf > 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 > params. > > Make sense? > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > > -- Ing. Gabriele Fatigati Parallel programmer CINECA Systems & Tecnologies Department Supercomputing Group Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy www.cineca.it Tel: +39 051 6171722 g.fatigati [AT] cineca.it
