I don’t think your stated analysis is quite correct. First, the topology is
-always- retrieved. The only question is whether or not we set the #slots equal
to the number of detected cpus.
If the user specifies the #slots, then we respect that designation. If the user
does not specify #slots, th
Folks,
i ran some more test and found this
with both master and v2.x :
mpirun --host n0:16,n1:16 -np 4 --tag-output hostname | sort
[1,0]:n0
[1,1]:n0
[1,2]:n0
[1,3]:n0
and same output with the --map-by socket option.
now, without specifying the number of slots per hosts, and the
--oversub
Folks,
currently, default mapping policy on master is different than v2.x.
my preliminary question is : when will the master mapping policy land
into the release branch ?
v2.0.0 ? v2.x ? v3.0.0 ?
here are some commands and their output (both n0 and n1 have 16 cores
each, mpirun runs on n0)
