d396f0a6fc
1. replacing mpi_paffinity_alone with opal_paffinity_alone - for back-compatibility, I have aliased mpi_paffinity_alone to the new param name. This caus es a mild abstraction break in the opal/mca/paffinity framework - per the devel discussion...live with it. :-) I also moved the ompi_xxx global variable that tracked maffinity setup so it could be properly closed in MPI_Finalize to the opal/mca/maffinity framework to avoid an abstraction break. 2. Added code to the odls/default module to perform paffinity binding and maffinity init between process fork and exec. This has been tested on IU's odi n cluster and works for both MPI and non-MPI apps. 3. Revise MPI_Init to detect if affinity has already been set, and to attempt to set it if not already done. I have *not* tested this as I haven't yet f igured out a way to do so - I couldn't get slurm to perform cpu bindings, even though it supposedly does do so. This has only been lightly tested and would definitely benefit from a wider range of evaluation... This commit was SVN r21209.
91 строка
2.8 KiB
Plaintext
91 строка
2.8 KiB
Plaintext
# -*- text -*-
|
|
#
|
|
# Copyright (c) 2004-2007 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$
|
|
#
|
|
# This is the US/English general help file for Open RTE's orted launcher.
|
|
#
|
|
|
|
[odls-default:could-not-kill]
|
|
WARNING: A process refused to die!
|
|
|
|
Host: %s
|
|
PID: %d
|
|
|
|
This process may still be running and/or consuming resources.
|
|
|
|
[odls-default:could-not-send-kill]
|
|
WARNING: A process refused the kill SIGTERM signal!
|
|
This should never happen unless the application is changing the
|
|
parent/child relationship permissions.
|
|
|
|
Host: %s
|
|
PID: %d
|
|
Errno: %d
|
|
|
|
This process may still be running and/or consuming resources.
|
|
|
|
[orte-odls-default:execv-error]
|
|
Could not execute the executable "%s": %s
|
|
|
|
This could mean that your PATH or executable name is wrong, or that you do not
|
|
have the necessary permissions. Please ensure that the executable is able to be
|
|
found and executed.
|
|
|
|
#
|
|
[nodeid-out-of-range]
|
|
The id of a node is out of the allowed range.
|
|
|
|
Value given: %ld
|
|
Max value allowed: %ld
|
|
|
|
This may be resolved by increasing the number of available node id's by
|
|
re-configuring Open MPI with the --enable-jumbo-clusters option, and then
|
|
re-running the application
|
|
#
|
|
[odls-default:multiple-paffinity-schemes]
|
|
Multiple processor affinity schemes were specified (can only specify one):
|
|
|
|
Slot list: %s
|
|
opal_paffinity_alone: true
|
|
|
|
Please specify only the one desired method.
|
|
#
|
|
[odls-default:slot-list-failed]
|
|
We were unable to successfully process/set the requested processor
|
|
affinity settings:
|
|
|
|
Specified slot list: %s
|
|
Error: %s
|
|
|
|
This could mean that a non-existent processor was specified, or
|
|
that the specification had improper syntax.
|
|
#
|
|
[odls-default:invalid-node-rank]
|
|
An invalid node rank was obtained - this is probably something
|
|
that should be reported to the OMPI developers.
|
|
#
|
|
[odls-default:invalid-phys-cpu]
|
|
An invalid physical processor id was returned when attempting to
|
|
set processor affinity. This is probably something that should be
|
|
reported to the OMPI developers - your system may not support
|
|
this functionality.
|
|
#
|
|
[odls-default:failed-set-paff]
|
|
An attempt to set processor affinity has failed - please check to
|
|
ensure that your system supports such functionality. If so, then
|
|
this is probably something that should be reported to the OMPI developers.
|