Dear Open MPIers,
Automatic tuning of socket buffers has been in the linux kernel since
2.4.17/2.6.7. That is some time ago. I remember, at the time, that we removed
the default setsockopt() for SO_SNDBUF and SO_RCVBUF in Scali MPI.
Today, running Open MPI 1.10.2 using the TCP BTL, on a
To me, it looks like Open MPI in xoob_send_qp_connect() attempts to set the
max_dest_rd_atomic attribute in the transition from INIT to RTR, even for
XRC_INI QPs. This is illegal, according to the ib_modify_qp_is_ok() function in
ib_core. In particular, IBV_QP_MAX_DEST_RD_ATOMIC is not part of
With patch
https://github.com/torvalds/linux/commit/e15f431fe2d53cd4673510736da7d4fa1090e096,
the use of ENOSYS has been clarified.
/*
* This error code is special: arch syscall entry code will return
* -ENOSYS if users try to call a syscall that doesn't exist. To keep
* failures of
From time-to-time, and have a need for running Open MPI apps using the openib
btl on a single node, where port 1 on the HCA is connected to port 2 on the
same HCA.
Using a vintage 1.5.4, my command line would read:
mpiexec --mca btl self,openib --mca btl_openib_cpc_include oob \
-np 1
