I’ve begun getting this annoyingly generic warning, too. It appears to be
coming from the openib provider. If you disable it with -mtl ^openib the
warning goes away.
Sent from my iPad
> On Mar 13, 2021, at 3:28 PM, Bob Beattie via users
> wrote:
>
> Hi everyone,
>
> To be honest, as an MPI
Thanks George,
Pierre
> On 13 Mar 2021, at 22:24, George Bosilca wrote:
>
> Hi Pierre,
>
> MPI is allowed to pipeline the collective communications. This explains why
> the MPI_Op takes the len of the buffers as an argument. Because your MPI_Op
> ignores this length it alters data outside t
Hi Pierre,
MPI is allowed to pipeline the collective communications. This explains why
the MPI_Op takes the len of the buffers as an argument. Because your MPI_Op
ignores this length it alters data outside the temporary buffer we use for
the segment. Other versions of the MPI_Allreduce implementat
Hi everyone,
To be honest, as an MPI / IB noob, I don't know if this falls under
OpenMPI or Mellanox
Am running a small cluster of HP DL380 G6/G7 machines.
Each runs Ubuntu server 20.04 and has a Mellanox ConnectX-3 card,
connected by an IS dumb switch.
When I begin my MPI program (snappy
Hello,
The following piece of code generates Valgrind errors with OpenMPI 4.1.0, while
it is Valgrind-clean with MPICH and OpenMPI 4.0.5.
I don’t think I’m doing anything illegal, so could this be a regression
introduced in 4.1.0?
Thanks,
Pierre
$ /opt/openmpi-4.1.0/bin/mpicxx ompi.cxx -g -O0 -
