ad that option solved the problem. We’ll
> have to look at that configure option - shouldn’t be too hard.
>
> As for the mapping you requested - no problem! Here’s the cmd line:
>
> mpirun --map-by ppr:1:core --bind-to hwthread
>
> Ralph
>
>> On Apr 19, 2017, at 2:51
t; As I said earlier in this thread, we are actively working with the OpenMP
> folks on a mechanism by which the two sides can coordinate these actions so
> it will be easier to get the desired behavior. For now, though, hopefully
> this will suffice.
>
>> On Apr 13, 2017
On 13.04.2017 15:20, gil...@rist.or.jp wrote:
...
> in your second case, there are 2 things
> - MPI binds to socket, that is why two MPI tasks are assigned the same
> hyperthreads
> - the GNU OpenMP runtime looks unable to figure out 2 processes use the
> same cores, and hence end up binding
>
> propagated
>
> can you try
>
> mpirun -x OMP_PROC_BIND ...
>
> and see if it helps ?
>
>
> Cheers,
>
>
> On 4/13/2017 12:23 AM, Heinz-Ado Arnolds wrote:
>> Dear Gilles,
>>
>> thanks for your answer.
>>
>> - compiler: gcc
ould not worry about them migrating between hyperthreads from the same
> core.
>
> Cheers,
>
> Gilles
>
> On Wednesday, April 12, 2017, Heinz-Ado Arnolds <mailto:arno...@mpa-garching.mpg.de>> wrote:
>
> Dear rhc,
>
> to make it more clear what I
can override that by
> adding "-bind-to core" to your cmd line if that is what you desire.
>
> If you want to use individual HTs as independent processors, then
> “--use-hwthread-cpus -bind-to hwthreads” would indeed be the right
> combination.
>
>>
d-cpus, --bind-to hwthreads,
but didn't find the right combination.
Would be great to get any hints?
Thank a lot in advance,
Heinz-Ado Arnolds
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
-mpi/ompi/pull/3163
>
>
>> On Mar 22, 2017, at 7:49 AM, Reuti > <mailto:re...@staff.uni-marburg.de>> wrote:
>>
>>>
>>> Am 22.03.2017 um 15:31 schrieb Heinz-Ado Arnolds
>>> mailto:arno...@mpa-garching.mpg.de>>:
>>>
>>&g
of a way to revert to the old style (e.g. configure
option)? Otherwise all my users have to add this option.
Thanks again, and have a nice day
Ado Arnolds
On 22.03.2017 13:58, Reuti wrote:
> Hi,
>
>> Am 22.03.2017 um 10:44 schrieb Heinz-Ado Arnolds
>> :
>>
>> Dear
way to revert the 2.1.0 behavior to the 1.10.6 (use SGE/qrsh) one?
Are there mca params to set this?
If you need more info, please let me know. (Job submitting machine and target
cluster are the same with all tests. SW is residing in AFS directories visible
on all machines
10 matches
Mail list logo
