2011-04-26 13:31:07 +00:00
|
|
|
# -*- text -*-
|
|
|
|
|
#
|
2014-01-22 12:17:14 +00:00
|
|
|
# Copyright (c) 2011-2014 Cisco Systems, Inc. All rights reserved.
|
2014-01-15 14:48:39 +00:00
|
|
|
# Copyright (c) 2014 Intel, Inc. All rights reserved.
|
2011-04-26 13:31:07 +00:00
|
|
|
# $COPYRIGHT$
|
|
|
|
|
#
|
|
|
|
|
# Additional copyrights may follow
|
|
|
|
|
#
|
|
|
|
|
# $HEADER$
|
|
|
|
|
#
|
2011-09-19 16:10:37 +00:00
|
|
|
# This is the US/English help file for Open MPI's hwloc base support
|
2011-04-26 13:31:07 +00:00
|
|
|
#
|
|
|
|
|
[mbind failure]
|
|
|
|
|
Open MPI failed to bind internal memory to a specific NUMA node. This
|
|
|
|
|
message will only be reported at most once per process.
|
|
|
|
|
|
|
|
|
|
Local host: %s
|
|
|
|
|
PID: %d
|
|
|
|
|
File: %s:%d
|
|
|
|
|
Message: %s
|
|
|
|
|
Severity: %s
|
At long last, the fabled revision to the affinity system has arrived. A more detailed explanation of how this all works will be presented here:
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.
2011-11-15 03:40:11 +00:00
|
|
|
#
|
2012-08-29 16:40:46 +00:00
|
|
|
[invalid binding_policy]
|
At long last, the fabled revision to the affinity system has arrived. A more detailed explanation of how this all works will be presented here:
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.
2011-11-15 03:40:11 +00:00
|
|
|
The specified %s policy is not recognized:
|
|
|
|
|
|
|
|
|
|
Policy: %s
|
|
|
|
|
|
|
|
|
|
Please check for a typo or ensure that the option is a supported
|
|
|
|
|
one.
|
|
|
|
|
#
|
2014-11-09 20:50:12 -08:00
|
|
|
[cpu-not-found]
|
|
|
|
|
A specified %s processor does not exist in this topology:
|
At long last, the fabled revision to the affinity system has arrived. A more detailed explanation of how this all works will be presented here:
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.
2011-11-15 03:40:11 +00:00
|
|
|
|
2014-11-09 20:50:12 -08:00
|
|
|
CPU number: %d
|
At long last, the fabled revision to the affinity system has arrived. A more detailed explanation of how this all works will be presented here:
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.
2011-11-15 03:40:11 +00:00
|
|
|
Cpu set given: %s
|
|
|
|
|
#
|
|
|
|
|
[redefining-policy]
|
|
|
|
|
Conflicting directives for binding policy are causing the policy
|
|
|
|
|
to be redefined:
|
|
|
|
|
|
|
|
|
|
New policy: %s
|
|
|
|
|
Prior policy: %s
|
|
|
|
|
|
|
|
|
|
Please check that only one policy is defined.
|
2014-01-15 14:48:39 +00:00
|
|
|
#
|
|
|
|
|
[deprecated]
|
2014-01-22 12:17:14 +00:00
|
|
|
The following command line option and corresponding MCA parameter have
|
|
|
|
|
been deprecated and replaced as follows:
|
2014-01-15 14:48:39 +00:00
|
|
|
|
|
|
|
|
Command line option:
|
|
|
|
|
Deprecated: %s
|
|
|
|
|
Replacement: %s
|
|
|
|
|
|
2014-01-22 12:17:14 +00:00
|
|
|
Equivalent MCA parameter:
|
|
|
|
|
Deprecated: %s
|
2014-01-15 14:48:39 +00:00
|
|
|
Replacement: %s
|
|
|
|
|
|
2014-01-22 12:17:14 +00:00
|
|
|
The deprecated forms *will* disappear in a future version of Open MPI.
|
2014-01-15 14:48:39 +00:00
|
|
|
Please update to the new syntax.
|
2014-04-07 15:39:54 +00:00
|
|
|
#
|
|
|
|
|
[obj-idx-failed]
|
|
|
|
|
Open MPI failed to find a cache of a specified type. This is a highly
|
|
|
|
|
unusual error; it may indicate a system configuration error. This
|
|
|
|
|
additional information may be of help:
|
|
|
|
|
|
|
|
|
|
Message: %s
|
|
|
|
|
Cache level: %d
|