> On Nov 20, 2017, at 7:02 PM, r...@open-mpi.org wrote:
>
> So there are two options here that will work and hopefully provide you with
> the desired pattern:
>
> * if you want the procs to go in different NUMA regions:
> $ mpirun --map-by numa:PE=2 --report-bindings -n 2 /bin/true
> [rhc001:13
I believe that map-by core with a PE > 1 may have worked at some point in the
past, but the docs should probably be looked at. I took a (very brief) look at
the code and re-enabling that particular option would be difficult and not
really necessary since one can reproduce the desired pattern wit
Hi Howard/OpenMPI Users,
I have had a similar seg-fault this week using OpenMPI 2.1.1 with GCC 4.9.3 so
I tried to compile the example code in the email below. I see similar behavior
to a small benchmark we have in house (but using inc not finc).
When I run on a single node (both PE’s on the sa
Hi,
I am finding that on Ctrl-C, mpirun immediately stops and does not sends
SIGTERM to the child processes.
I am using openmpi 1.10.6.
The child processes are able to handle SIGINT. I verified that by a printf in
my signal handler and then issuing SIGINT to my process directly. However, when
Try upgrading to the v3.0, or at least to the latest in the v2.x series. The
v1.10 series is legacy and no longer maintained.
> On Nov 21, 2017, at 8:20 AM, Kulshrestha, Vipul
> wrote:
>
> Hi,
>
> I am finding that on Ctrl-C, mpirun immediately stops and does not sends
> SIGTERM to the chil
> What version of Open MPI are you trying to use?
Open MPI 2.1.1-2 as distributed by Arch Linux.
> Also, could you describe something about your system.
This is all in shared memory on a MacBook Pro; no networking involved.
The seg fault with the code example above looks like this:
[xiii@shini
