This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
dplace is a general purpose tool for placing applications and doesn't
know anything about MPI. It does do internal accounting system wide to
spread and pin processes and threads. For example if you run a job with
dplace and tell it to just pin your job anywhere it can and another user
does the same, if there are enough cores / hyperthreads available it
will keep the jobs from being pinned to the same cores / hyperthreads.
Brice Goglin wrote:
> Does dplace do something clever like reading the MPI rank and
> communicator size and try to figure out how to distribute among the
> cores so as to maximize memory bandwidth or cache sharing ?
> Michael Raymond wrote:
>> As of SGI ProPack 7 dplace uses hwloc internally to specify stride
>> patterns. For example:
>> mpirun -np 8 dplace -c SC a.out
>> means to pin ranks to every core inside a socket before jumping to the
>> next socket and doing the same.
>> From the man page:
>> For striding patterns any
>> subset of the characters (B)lade, (S)ocket, (C)ore,
>> (T)hread may
>> be used and their ordering specifies the nesting of the
>> tion. For example "SC" means to iterate all the
>> cores in a
>> socket before moving to the next CPU socket, while "CB"
>> means to
>> pin to the first core of each blade, then the second
>> core of
>> every blade, etc.
>> I've been trying to evangelize more hwloc usage with mixed results.
>> Brice Goglin wrote:
>>> I discovered "dplace" today. I don't know how many people install/use it
>>> on their cluster, but it's something that looks interesting when you
>>> don't have advanced binding capabilities in the MPI implementation. For
>>> instance, you could do:
>>> $ mpirun -np 8 dplace 0,4,2,6,1,5,3,7 myprogram
>>> to bind process ranks according to the machine topology.
>>> hwloc-calc can easily generate such list of physical processors, for
>>> $ hwloc-calc --physical proc:all --pulist
>>> or even restrict of one PU per socket with:
>>> $ hwloc-calc --physical socket:all.core:0 --pulist
>>> So hwloc-calc could help dplace significantly. Maybe we should put such
>>> examples somewhere in the doc.
>>> hwloc-devel mailing list
> hwloc-devel mailing list
Michael A. Raymond
Message Passing Toolkit Team
Silicon Graphics Inc