This commit introduces a new "mindist" ORTE RMAPS mapper, as well as
some relevant updates/new functionality in the opal/mca/hwloc and
orte/mca/rmaps bases. This work was mainly developed by Mellanox,
with a bunch of advice from Ralph Castain, and some minor advice from
Brice Goglin and Jeff Squyres.
Even though this is mainly Mellanox's work, Jeff is committing only
for logistical reasons (he holds the hg+svn combo tree, and can
therefore commit it directly back to SVN).
-----
Implemented distance-based mapping algorithm as a new "mindist"
component in the rmaps framework. It allows mapping processes by NUMA
due to PCI locality information as reported by the BIOS - from the
closest to device to furthest.
To use this algorithm, specify:
{{{mpirun --map-by dist:<device_name>}}}
where <device_name> can be mlx5_0, ib0, etc.
There are two modes provided:
1. bynode: load-balancing across nodes
1. byslot: go through slots sequentially (i.e., the first nodes are
more loaded)
These options are regulated by the optional ''span'' modifier; the
command line parameter looks like:
{{{mpirun --map-by dist:<device_name>,span}}}
So, for example, if there are 2 nodes, each with 8 cores, and we'd
like to run 10 processes, the mindist algorithm will place 8 processes
to the first node and 2 to the second by default. But if you want to
place 5 processes to each node, you can add a span modifier in your
command line to do that.
If there are two NUMA nodes on the node, each with 4 cores, and we run
6 processes, the mindist algorithm will try to find the NUMA closest
to the specified device, and if successful, it will place 4 processes
on that NUMA but leaving the remaining two to the next NUMA node.
You can also specify the number of cpus per MPI process. This option
is handled so that we map as many processes to the closest NUMA as we
can (number of available processors at the NUMA divided by number of
cpus per rank) and then go on with the next closest NUMA.
The default binding option for this mapping is bind-to-numa. It works
if you don't specify any binding policy. But if you specified binding
level that was "lower" than NUMA (i.e hwthread, core, socket) it would
bind to whatever level you specify.
This commit was SVN r28552.
2013-05-22 13:04:40 +00:00
|
|
|
# -*- text -*-
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
|
|
|
# University Research and Technology
|
|
|
|
|
# Corporation. All rights reserved.
|
|
|
|
|
# Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
|
|
|
# of Tennessee Research Foundation. All rights
|
|
|
|
|
# reserved.
|
|
|
|
|
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
|
|
|
# University of Stuttgart. All rights reserved.
|
|
|
|
|
# Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
|
# All rights reserved.
|
|
|
|
|
# $COPYRIGHT$
|
|
|
|
|
#
|
|
|
|
|
# Additional copyrights may follow
|
|
|
|
|
#
|
|
|
|
|
# $HEADER$
|
|
|
|
|
#
|
|
|
|
|
#
|
|
|
|
|
[multi-apps-and-zero-np]
|
|
|
|
|
Open MPI found multiple applications to be launched, and at least one
|
|
|
|
|
that failed to specify the number of processes to execute. When
|
|
|
|
|
specifying multiple applications, you must specify how many processes
|
|
|
|
|
of each to launch via the -np argument.
|
|
|
|
|
#
|
|
|
|
|
[orte-rmaps-mindist:no-pci-locality-info]
|
2013-12-12 15:30:29 +00:00
|
|
|
No PCI locality information could be found on at least one node. Please, upgrade BIOS to expose NUMA info.
|
This commit introduces a new "mindist" ORTE RMAPS mapper, as well as
some relevant updates/new functionality in the opal/mca/hwloc and
orte/mca/rmaps bases. This work was mainly developed by Mellanox,
with a bunch of advice from Ralph Castain, and some minor advice from
Brice Goglin and Jeff Squyres.
Even though this is mainly Mellanox's work, Jeff is committing only
for logistical reasons (he holds the hg+svn combo tree, and can
therefore commit it directly back to SVN).
-----
Implemented distance-based mapping algorithm as a new "mindist"
component in the rmaps framework. It allows mapping processes by NUMA
due to PCI locality information as reported by the BIOS - from the
closest to device to furthest.
To use this algorithm, specify:
{{{mpirun --map-by dist:<device_name>}}}
where <device_name> can be mlx5_0, ib0, etc.
There are two modes provided:
1. bynode: load-balancing across nodes
1. byslot: go through slots sequentially (i.e., the first nodes are
more loaded)
These options are regulated by the optional ''span'' modifier; the
command line parameter looks like:
{{{mpirun --map-by dist:<device_name>,span}}}
So, for example, if there are 2 nodes, each with 8 cores, and we'd
like to run 10 processes, the mindist algorithm will place 8 processes
to the first node and 2 to the second by default. But if you want to
place 5 processes to each node, you can add a span modifier in your
command line to do that.
If there are two NUMA nodes on the node, each with 4 cores, and we run
6 processes, the mindist algorithm will try to find the NUMA closest
to the specified device, and if successful, it will place 4 processes
on that NUMA but leaving the remaining two to the next NUMA node.
You can also specify the number of cpus per MPI process. This option
is handled so that we map as many processes to the closest NUMA as we
can (number of available processors at the NUMA divided by number of
cpus per rank) and then go on with the next closest NUMA.
The default binding option for this mapping is bind-to-numa. It works
if you don't specify any binding policy. But if you specified binding
level that was "lower" than NUMA (i.e hwthread, core, socket) it would
bind to whatever level you specify.
This commit was SVN r28552.
2013-05-22 13:04:40 +00:00
|
|
|
|
|
|
|
|
Node: %s
|
|
|
|
|
|
2013-11-13 09:26:40 +00:00
|
|
|
Open MPI will map the application by default (BYSLOT).
|
2013-08-28 16:23:33 +00:00
|
|
|
#
|
2013-12-12 15:30:29 +00:00
|
|
|
[orte-rmaps-mindist:several-devices]
|
|
|
|
|
On at least one node, more than one of the specified device was discovered.
|
2013-12-09 06:34:38 +00:00
|
|
|
In this scenario, passing the 'auto' option to the rmaps minimum
|
2013-12-12 15:30:29 +00:00
|
|
|
distance mapper is ambiguous and therefore not valid.
|
|
|
|
|
Please select the particular device that you would like
|
2015-03-31 11:46:48 +03:00
|
|
|
to be mapped nearest via -mca rmaps_dist_device <device> option,
|
|
|
|
|
e.g. --map-by dist -mca rmaps_dist_device mlx4_0.
|
2013-08-28 16:23:33 +00:00
|
|
|
|
2013-12-12 15:30:29 +00:00
|
|
|
Device type: %s
|
|
|
|
|
#Devices: %d
|
2013-08-28 16:23:33 +00:00
|
|
|
Node: %s
|
|
|
|
|
|
2013-11-13 09:26:40 +00:00
|
|
|
Open MPI will map the application by default (BYSLOT).
|
2013-08-29 20:01:06 +00:00
|
|
|
#
|
|
|
|
|
[orte-rmaps-mindist:device-not-found]
|
2013-12-12 15:30:29 +00:00
|
|
|
The specified device type cannot be found on at least one node.
|
2013-08-29 20:01:06 +00:00
|
|
|
|
|
|
|
|
Device: %s
|
|
|
|
|
Node: %s
|
|
|
|
|
|
2013-11-13 09:26:40 +00:00
|
|
|
Open MPI will map the application by default (BYSLOT).
|