6310361532
https://svn.open-mpi.org/trac/ompi/wiki/ProcessPlacement The wiki page is incomplete at the moment, but I hope to complete it over the next few days. I will provide updates on the devel list. As the wiki page states, the default and most commonly used options remain unchanged (except as noted below). New, esoteric and complex options have been added, but unless you are a true masochist, you are unlikely to use many of them beyond perhaps an initial curiosity-motivated experimentation. In a nutshell, this commit revamps the map/rank/bind procedure to take into account topology info on the compute nodes. I have, for the most part, preserved the default behaviors, with three notable exceptions: 1. I have at long last bowed my head in submission to the system admin's of managed clusters. For years, they have complained about our default of allowing users to oversubscribe nodes - i.e., to run more processes on a node than allocated slots. Accordingly, I have modified the default behavior: if you are running off of hostfile/dash-host allocated nodes, then the default is to allow oversubscription. If you are running off of RM-allocated nodes, then the default is to NOT allow oversubscription. Flags to override these behaviors are provided, so this only affects the default behavior. 2. both cpus/rank and stride have been removed. The latter was demanded by those who didn't understand the purpose behind it - and I agreed as the users who requested it are no longer using it. The former was removed temporarily pending implementation. 3. vm launch is now the sole method for starting OMPI. It was just too darned hard to maintain multiple launch procedures - maybe someday, provided someone can demonstrate a reason to do so. As Jeff stated, it is impossible to fully test a change of this size. I have tested it on Linux and Mac, covering all the default and simple options, singletons, and comm_spawn. That said, I'm sure others will find problems, so I'll be watching MTT results until this stabilizes. This commit was SVN r25476.
71 строка
1.9 KiB
Plaintext
71 строка
1.9 KiB
Plaintext
# -*- text -*-
|
|
#
|
|
# Copyright (c) 2011 Cisco Systems, Inc. All rights reserved.
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
#
|
|
[invalid-ppr]
|
|
An invalid value was given for the number of processes
|
|
per resource (ppr) to be mapped on each node:
|
|
|
|
PPR: %s
|
|
|
|
The specification must be a comma-separated list containing
|
|
combinations of number, followed by a colon, followed
|
|
by the resource type. For example, a value of "1:socket" indicates that
|
|
one process is to be mapped onto each socket. Values are supported
|
|
for hwthread, core, L1-3 caches, socket, numa, and node. Note that
|
|
enough characters must be provided to clearly specify the desired
|
|
resource (e.g., "nu" for "numa").
|
|
#
|
|
[unrecognized-ppr-option]
|
|
An unrecognized value was given for the number of processes
|
|
per resource (ppr) to be mapped on each node:
|
|
|
|
Value: %s
|
|
PPR: %s
|
|
|
|
The specification must be a number, followed by a colon, followed
|
|
by the resource type. For example, a value of "1:slot" indicates that
|
|
anything over one process per slot is to be considered oversubscribed.
|
|
Only values for "hwthread", "core", "socket",
|
|
"l1cache", "l2cache", "l3cache", "numa", and "node" are allowed. Note that
|
|
enough characters must be provided to clearly specify the desired
|
|
resource (e.g., "nu" for "numa").
|
|
#
|
|
[ppr-violation]
|
|
The provided mapping directives resulted in too many processes
|
|
being placed on a node:
|
|
|
|
Node: %s
|
|
Num procs: %d
|
|
Limiting resource: %s
|
|
Num resources: %d
|
|
Specified constraint: %s
|
|
|
|
Please adjust and try again.
|
|
#
|
|
[ppr-too-many-procs]
|
|
Your job has requested more processes than the ppr for
|
|
this topology can support:
|
|
|
|
App: %s
|
|
Number of procs: %d
|
|
PPR: %s
|
|
|
|
Please revise the conflict and try again.
|
|
#
|
|
[ppr-topo-missing]
|
|
A ppr pattern was specified, but the topology information
|
|
for the following node is missing:
|
|
|
|
Node: %s
|
|
|
|
Please ensure that vm launch mode is enabled, either via the
|
|
-vm option to mpirun or using the orte_vm_launch MCA
|
|
parameter.
|