Ralph,
I suspect ompi tries to bind to threads outside the cpuset.
this could be pretty similar to a previous issue when ompi tried to bind to
cores outside the cpuset.
/* when a core has more than one thread, would ompi assume all the threads
are available if the core is available ? */
I will inv
Hi, all,
I played a bit more and it seems that the problem results from
trg_obj = opal_hwloc_base_find_min_bound_target_under_obj()
called in rmaps_base_binding.c / bind_downwards being wrong. I do not
know the reason, but I think I know when the problem happens (at least
on 1.10.1rc1). It se
Marcin,
i ran a simple test with v1.10.1rc1 under a cpuset with
- one core (two threads 0,16) on socket 0
- two cores (two threads each 8,9,24,25) on socket 1
$ mpirun -np 3 -bind-to core ./hello_c
--
A request was made to b
I would consider that a bug, myself - if there is some resource available, we
should use it
> On Oct 4, 2015, at 5:42 PM, Gilles Gouaillardet wrote:
>
> Marcin,
>
> i ran a simple test with v1.10.1rc1 under a cpuset with
> - one core (two threads 0,16) on socket 0
> - two cores (two threads e
