But in many ways, it’s also not helpful to change the MTU from Open MPI. It
sounds like you made a bunch of changes all at once; I’d break them down and
build up. MTU is a very system-level configuration. Use a tcp transmission
test (iperf, etc.) to make sure TCP connections work between the
Alberto,
Are you saying the program hang even without jumbo frame (aka 1500 MTU) ?
At first, make sure there is no firewall running, and then you can try
mpirun --mca btl tcp,vader,self --mca oob_tcp_if_include eth0 --mca
btl_tcp_if_include eth0 ...
(Replace eth0 with the interface name you want
"ompi_info --param btl tcp -l 9" will give you all the TCP options.
Unfortunately, OMPI does not support programatically changing the value of
the MTU.
George.
PS: We would be happy to receive contributions from the community.
On Fri, May 5, 2017 at 10:29 AM, Alberto Ortiz
wrote:
> I am usi
I am using version 1.10.6 on archlinux.
The option I should pass to mpirun should then be "-mca btl_tcp_mtu 13000"?
Just to be sure.
Thank you,
Alberto
El 5 may. 2017 16:26, "r...@open-mpi.org" escribió:
> If you are looking to use TCP packets, then you want to set the send/recv
> buffer size in
If you are looking to use TCP packets, then you want to set the send/recv
buffer size in the TCP btl, not the openib one, yes?
Also, what version of OMPI are you using?
> On May 5, 2017, at 7:16 AM, Alberto Ortiz wrote:
>
> Hi,
> I have a program running with openMPI over a network using a gig
Hi,
I have a program running with openMPI over a network using a gigabit
switch. This switch supports jumbo frames up to 13.000 bytes, so, in order
to test and see if it would be faster communicating with this frame
lengths, I am trying to use them with my program. I have set the MTU in
each node t
