Thanks Mikhail,
You have a good point.
With the current semantic used in the IMB benchmark, this cannot be
equivalent to
MPI_Reduce() of N bytes followed by MPI_Scatterv() of N bytes.
So this is indeed a semantical question :
what should be a MPI_Reduce_scatter() of N bytes equivalent
Hi,
The memory manager of IMB (IMB_mem_manager.c) do not support the
MPI_Reduce_scatter operation. It allocates too small send buffer:
sizeof(msg), but the operation requires commsize * sizeof(msg).
There are two possible solutions:
1) Fix computations of recvcounts (as proposed by Gilles)
Thanks for the report.
As far as I am concerned, this is a bug in the IMB benchmark, and I
issued a PR to fix that
https://github.com/intel/mpi-benchmarks/pull/11
Meanwhile, you can manually download and apply the patch at
https://github.com/intel/mpi-benchmarks/pull/11.patch
Cheers,
On Tue, 4 Dec 2018 09:15:13 -0500
George Bosilca wrote:
> I'm trying to replicate using the same compiler (icc 2019) on my OSX
> over TCP and shared memory with no luck so far. So either the
> segfault it's something specific to OmniPath or to the memcpy
> implementation used on Skylake.
Note
I'm trying to replicate using the same compiler (icc 2019) on my OSX over
TCP and shared memory with no luck so far. So either the segfault it's
something specific to OmniPath or to the memcpy implementation used on
Skylake. I tried to use the trace you sent, more specifically the
On Mon, 3 Dec 2018 19:41:25 +
"Hammond, Simon David via users" wrote:
> Hi Open MPI Users,
>
> Just wanted to report a bug we have seen with OpenMPI 3.1.3 and 4.0.0
> when using the Intel 2019 Update 1 compilers on our
> Skylake/OmniPath-1 cluster. The bug occurs when running the Github
>
