I see, thanks for the quick reply. In light of this, I'd like to suggest an update to the FAQ entry at http://www.open-mpi.org/faq/?category=tuning#available-mca-params I just noticed that this is covered in question 6, but it is not clear when reading question 8.
Tom > On Thu, 2 Jul 2015 at 14:17:17, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > Greetings Tom. > This was a change we made to the default behavior in ompi_info in the > v1.7/v1.8 series. See the --level option and the "Levels" section in the > ompi_info(1) man page (i.e., > http://www.open-mpi.org/doc/v1.8/man1/ompi_info.1.php). > On Jul 2, 2015, at 10:10 AM, Tom Coles <tco...@mit.edu> wrote: > > When I run: > ompi_info --param btl all > with OpenMPI 1.8.x, it returns only btl_tcp_if_include and > btl_tcp_if_exclude. However, if I run it in 1.6.x, it returns a long list of > btl parameters. These parameters are still shown in 1.8.x if I run: > ompi_info --all > But obviously this is less convenient when I am only interested in btl > parameters. > > I'm not sure if this is a bug with the first command I gave above or if > something has changed that I'm not aware of. > > I run RHEL 5.11 and have tried compiling with various GCC versions, including > 4.4.7 (from RedHat's yum repository), 4.8.2, 4.9.1, and 5.1. > > Thanks for any help/advice. > > Tom Coles > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2015/07/27246.php
