Well, it looks like the formatting on that mail did not translate well. Sorry
about that -- but at least it gives you an idea of what the new text looks like.
It will render better in a browser than it did in that email. :-)
> On Jul 2, 2015, at 1:05 PM, Jeff Squyres (jsquyres)
> wrote:
>
On Jul 2, 2015, at 12:20 PM, Tom Coles mailto:tco...@mit.edu>>
wrote:
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 i
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
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 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 w
