A couple of BTW's:
The manual mentions "-bind-to-core", but running the code shows that
this is obsolete,
and one must use "-bind-to core".
I can get the bindings by adding --report-bindings:
$ mpirun -np 2 --report-bindings -bind-to core affinity
[vcloud.txcorp.com:3231773] MCW rank 0 bound to socket 0[core 0[hwt
0-1]]:
[BB/../../../../../../../../../../../../../../../../../../../../../../..]
[vcloud.txcorp.com:3231773] MCW rank 1 bound to socket 0[core 1[hwt
0-1]]:
[../BB/../../../../../../../../../../../../../../../../../../../../../..]
Thx....
On 2/21/21 6:56 AM, John R Cary via users wrote:
OMPI_Affinity_str returning empty strings
I am trying to understand the affinities chosen by OpenMPI
following the documentation of
https://www.open-mpi.org/doc/v4.0/man3/OMPI_Affinity_str.3.php
CentOS-8.2, gcc-8.3, openmpi-4.0.5
$ which mpirun
~/ompi/contrib-gcc830/openmpi-4.0.5-shared/bin/mpirun
I have taken that program, named it "affinity", compiled and linked
with openmpi. I run it as documented and get
$ mpirun -np 2 -bind-to core affinity
rank 0:
ompi_bound:
current_binding:
exists:
rank 1:
ompi_bound:
current_binding:
exists:
As one can see, I get no output. Is there something I can change to
make this work?
Thx...John Cary
