Hi!
It is in so far related, that one of these threads is actually doing
something.
Btw, I noticed this on two separate machines! A computing cluster with
admin-built openmpi and Archlinux with openmpi from the repositories.
However, running the code with openmpi 1.6.2 and ifort 13.0.0 does
A singleton will indeed have an extra thread, but it should be quiescent. I’ll
check the 1.10.2 release candidate and see if it still exhibits that behavior.
> On Jan 7, 2016, at 9:32 PM, Au Eelis wrote:
>
> Hi!
>
> It is in so far related, that one of these threads is actually doing
> somet
Instead of MPI_Alloc_mem and MPI_Win_create, you should use
MPI_Win_allocate. This will make it much easier for the implementation to
optimize with interprocess shared memory and exploit scalability features
such as symmetric globally addressable memory. It also obviates the need
to do both MPI_W
