2006-09-15 01:29:51 +04:00
|
|
|
/*
|
2007-03-17 02:11:45 +03:00
|
|
|
* Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
|
2006-09-15 01:29:51 +04:00
|
|
|
* University Research and Technology
|
|
|
|
* Corporation. All rights reserved.
|
2008-11-01 03:39:46 +03:00
|
|
|
* Copyright (c) 2004-2008 The University of Tennessee and The University
|
2006-09-15 01:29:51 +04:00
|
|
|
* 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.
|
2009-05-22 18:59:27 +04:00
|
|
|
* Copyright (c) 2007-2009 Sun Microsystems, Inc. All rights reserved.
|
2007-10-17 17:47:36 +04:00
|
|
|
* Copyright (c) 2007 Evergrid, Inc. All rights reserved.
|
2008-06-09 18:53:58 +04:00
|
|
|
* Copyright (c) 2008 Cisco Systems, Inc. All rights reserved.
|
2007-10-17 17:47:36 +04:00
|
|
|
*
|
2006-09-15 01:29:51 +04:00
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "orte_config.h"
|
2008-02-28 04:57:57 +03:00
|
|
|
#include "orte/constants.h"
|
2009-07-13 06:29:17 +04:00
|
|
|
#include "orte/types.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2009-07-16 22:27:33 +04:00
|
|
|
#ifdef HAVE_STRING_H
|
2009-03-13 05:10:32 +03:00
|
|
|
#include <string.h>
|
|
|
|
#endif
|
2006-09-15 01:29:51 +04:00
|
|
|
#include <stdlib.h>
|
|
|
|
#ifdef HAVE_UNISTD_H
|
|
|
|
#include <unistd.h>
|
|
|
|
#endif
|
|
|
|
#include <errno.h>
|
2007-06-13 02:43:18 +04:00
|
|
|
#ifdef HAVE_SYS_TYPES_H
|
2006-09-15 01:29:51 +04:00
|
|
|
#include <sys/types.h>
|
2006-11-13 21:51:18 +03:00
|
|
|
#endif
|
2006-09-15 01:29:51 +04:00
|
|
|
#ifdef HAVE_SYS_WAIT_H
|
|
|
|
#include <sys/wait.h>
|
|
|
|
#endif
|
|
|
|
#include <signal.h>
|
|
|
|
#ifdef HAVE_FCNTL_H
|
|
|
|
#include <fcntl.h>
|
|
|
|
#endif
|
2006-11-13 21:51:18 +03:00
|
|
|
#ifdef HAVE_SYS_TIME_H
|
|
|
|
#include <sys/time.h>
|
|
|
|
#endif
|
2006-09-15 01:29:51 +04:00
|
|
|
#ifdef HAVE_SYS_PARAM_H
|
|
|
|
#include <sys/param.h>
|
|
|
|
#endif
|
|
|
|
#ifdef HAVE_NETDB_H
|
|
|
|
#include <netdb.h>
|
|
|
|
#endif
|
|
|
|
#ifdef HAVE_SYS_STAT_H
|
|
|
|
#include <sys/stat.h>
|
|
|
|
#endif /* HAVE_SYS_STAT_H */
|
|
|
|
|
2006-11-13 21:51:18 +03:00
|
|
|
#if defined(HAVE_SCHED_YIELD)
|
|
|
|
/* Only if we have sched_yield() */
|
|
|
|
#ifdef HAVE_SCHED_H
|
|
|
|
#include <sched.h>
|
|
|
|
#endif
|
|
|
|
#else
|
|
|
|
/* Only do these if we don't have <sched.h> */
|
|
|
|
#ifdef HAVE_SYS_SELECT_H
|
|
|
|
#include <sys/select.h>
|
|
|
|
#endif
|
|
|
|
#endif /* HAVE_SCHED_YIELD */
|
|
|
|
|
2009-05-12 06:18:35 +04:00
|
|
|
#include "opal/mca/maffinity/base/base.h"
|
|
|
|
#include "opal/mca/paffinity/base/base.h"
|
2009-07-13 06:29:17 +04:00
|
|
|
#include "opal/class/opal_pointer_array.h"
|
2009-05-12 06:18:35 +04:00
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
#include "orte/util/show_help.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/runtime/orte_wait.h"
|
2008-02-28 04:57:57 +03:00
|
|
|
#include "orte/runtime/orte_globals.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/mca/errmgr/errmgr.h"
|
2009-05-12 06:18:35 +04:00
|
|
|
#include "orte/mca/ess/ess.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/mca/iof/base/iof_base_setup.h"
|
2008-02-28 04:57:57 +03:00
|
|
|
#include "orte/util/name_fns.h"
|
These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC.
The commit has been tested for C/R and Cray operations, and on Odin (SLURM, rsh) and RoadRunner (TM). I tried to update all environments, but obviously could not test them. I know that Windows needs some work, and have highlighted what is know to be needed in the odls process component.
This represents a lot of work by Brian, Tim P, Josh, and myself, with much advice from Jeff and others. For posterity, I have appended a copy of the email describing the work that was done:
As we have repeatedly noted, the modex operation in MPI_Init is the single greatest consumer of time during startup. To-date, we have executed that operation as an ORTE stage gate that held the process until a startup message containing all required modex (and OOB contact info - see #3 below) info could be sent to it. Each process would send its data to the HNP's registry, which assembled and sent the message when all processes had reported in.
In addition, ORTE had taken responsibility for monitoring process status as it progressed through a series of "stage gates". The process reported its status at each gate, and ORTE would then send a "release" message once all procs had reported in.
The incoming changes revamp these procedures in three ways:
1. eliminating the ORTE stage gate system and cleanly delineating responsibility between the OMPI and ORTE layers for MPI init/finalize. The modex stage gate (STG1) has been replaced by a collective operation in the modex itself that performs an allgather on the required modex info. The allgather is implemented using the orte_grpcomm framework since the BTL's are not active at that point. At the moment, the grpcomm framework only has a "basic" component analogous to OMPI's "basic" coll framework - I would recommend that the MPI team create additional, more advanced components to improve performance of this step.
The other stage gates have been replaced by orte_grpcomm barrier functions. We tried to use MPI barriers instead (since the BTL's are active at that point), but - as we discussed on the telecon - these are not currently true barriers so the job would hang when we fell through while messages were still in process. Note that the grpcomm barrier doesn't actually resolve that problem, but Brian has pointed out that we are unlikely to ever see it violated. Again, you might want to spend a little time on an advanced barrier algorithm as the one in "basic" is very simplistic.
Summarizing this change: ORTE no longer tracks process state nor has direct responsibility for synchronizing jobs. This is now done via collective operations within the MPI layer, albeit using ORTE collective communication services. I -strongly- urge the MPI team to implement advanced collective algorithms to improve the performance of this critical procedure.
2. reducing the volume of data exchanged during modex. Data in the modex consisted of the process name, the name of the node where that process is located (expressed as a string), plus a string representation of all contact info. The nodename was required in order for the modex to determine if the process was local or not - in addition, some people like to have it to print pretty error messages when a connection failed.
The size of this data has been reduced in three ways:
(a) reducing the size of the process name itself. The process name consisted of two 32-bit fields for the jobid and vpid. This is far larger than any current system, or system likely to exist in the near future, can support. Accordingly, the default size of these fields has been reduced to 16-bits, which means you can have 32k procs in each of 32k jobs. Since the daemons must have a vpid, and we require one daemon/node, this also restricts the default configuration to 32k nodes.
To support any future "mega-clusters", a configuration option --enable-jumbo-apps has been added. This option increases the jobid and vpid field sizes to 32-bits. Someday, if necessary, someone can add yet another option to increase them to 64-bits, I suppose.
(b) replacing the string nodename with an integer nodeid. Since we have one daemon/node, the nodeid corresponds to the local daemon's vpid. This replaces an often lengthy string with only 2 (or at most 4) bytes, a substantial reduction.
(c) when the mca param requesting that nodenames be sent to support pretty error messages, a second mca param is now used to request FQDN - otherwise, the domain name is stripped (by default) from the message to save space. If someone wants to combine those into a single param somehow (perhaps with an argument?), they are welcome to do so - I didn't want to alter what people are already using.
While these may seem like small savings, they actually amount to a significant impact when aggregated across the entire modex operation. Since every proc must receive the modex data regardless of the collective used to send it, just reducing the size of the process name removes nearly 400MBytes of communication from a 32k proc job (admittedly, much of this comm may occur in parallel). So it does add up pretty quickly.
3. routing RML messages to reduce connections. The default messaging system remains point-to-point - i.e., each proc opens a socket to every proc it communicates with and sends its messages directly. A new option uses the orteds as routers - i.e., each proc only opens a single socket to its local orted. All messages are sent from the proc to the orted, which forwards the message to the orted on the node where the intended recipient proc is located - that orted then forwards the message to its local proc (the recipient). This greatly reduces the connection storm we have encountered during startup.
It also has the benefit of removing the sharing of every proc's OOB contact with every other proc. The orted routing tables are populated during launch since every orted gets a map of where every proc is being placed. Each proc, therefore, only needs to know the contact info for its local daemon, which is passed in via the environment when the proc is fork/exec'd by the daemon. This alone removes ~50 bytes/process of communication that was in the current STG1 startup message - so for our 32k proc job, this saves us roughly 32k*50 = 1.6MBytes sent to 32k procs = 51GBytes of messaging.
Note that you can use the new routing method by specifying -mca routed tree - if you so desire. This mode will become the default at some point in the future.
There are a few minor additional changes in the commit that I'll just note in passing:
* propagation of command line mca params to the orteds - fixes ticket #1073. See note there for details.
* requiring of "finalize" prior to "exit" for MPI procs - fixes ticket #1144. See note there for details.
* cleanup of some stale header files
This commit was SVN r16364.
2007-10-05 23:48:23 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "orte/mca/odls/base/odls_private.h"
|
|
|
|
#include "orte/mca/odls/default/odls_default.h"
|
|
|
|
|
2007-06-07 00:18:37 +04:00
|
|
|
/*
|
|
|
|
* External Interface
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
static int orte_odls_default_launch_local_procs(opal_buffer_t *data);
|
2009-07-13 06:29:17 +04:00
|
|
|
static int orte_odls_default_kill_local_procs(opal_pointer_array_t *procs, bool set_state);
|
2007-10-10 19:02:10 +04:00
|
|
|
static int orte_odls_default_signal_local_procs(const orte_process_name_t *proc, int32_t signal);
|
These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC.
The commit has been tested for C/R and Cray operations, and on Odin (SLURM, rsh) and RoadRunner (TM). I tried to update all environments, but obviously could not test them. I know that Windows needs some work, and have highlighted what is know to be needed in the odls process component.
This represents a lot of work by Brian, Tim P, Josh, and myself, with much advice from Jeff and others. For posterity, I have appended a copy of the email describing the work that was done:
As we have repeatedly noted, the modex operation in MPI_Init is the single greatest consumer of time during startup. To-date, we have executed that operation as an ORTE stage gate that held the process until a startup message containing all required modex (and OOB contact info - see #3 below) info could be sent to it. Each process would send its data to the HNP's registry, which assembled and sent the message when all processes had reported in.
In addition, ORTE had taken responsibility for monitoring process status as it progressed through a series of "stage gates". The process reported its status at each gate, and ORTE would then send a "release" message once all procs had reported in.
The incoming changes revamp these procedures in three ways:
1. eliminating the ORTE stage gate system and cleanly delineating responsibility between the OMPI and ORTE layers for MPI init/finalize. The modex stage gate (STG1) has been replaced by a collective operation in the modex itself that performs an allgather on the required modex info. The allgather is implemented using the orte_grpcomm framework since the BTL's are not active at that point. At the moment, the grpcomm framework only has a "basic" component analogous to OMPI's "basic" coll framework - I would recommend that the MPI team create additional, more advanced components to improve performance of this step.
The other stage gates have been replaced by orte_grpcomm barrier functions. We tried to use MPI barriers instead (since the BTL's are active at that point), but - as we discussed on the telecon - these are not currently true barriers so the job would hang when we fell through while messages were still in process. Note that the grpcomm barrier doesn't actually resolve that problem, but Brian has pointed out that we are unlikely to ever see it violated. Again, you might want to spend a little time on an advanced barrier algorithm as the one in "basic" is very simplistic.
Summarizing this change: ORTE no longer tracks process state nor has direct responsibility for synchronizing jobs. This is now done via collective operations within the MPI layer, albeit using ORTE collective communication services. I -strongly- urge the MPI team to implement advanced collective algorithms to improve the performance of this critical procedure.
2. reducing the volume of data exchanged during modex. Data in the modex consisted of the process name, the name of the node where that process is located (expressed as a string), plus a string representation of all contact info. The nodename was required in order for the modex to determine if the process was local or not - in addition, some people like to have it to print pretty error messages when a connection failed.
The size of this data has been reduced in three ways:
(a) reducing the size of the process name itself. The process name consisted of two 32-bit fields for the jobid and vpid. This is far larger than any current system, or system likely to exist in the near future, can support. Accordingly, the default size of these fields has been reduced to 16-bits, which means you can have 32k procs in each of 32k jobs. Since the daemons must have a vpid, and we require one daemon/node, this also restricts the default configuration to 32k nodes.
To support any future "mega-clusters", a configuration option --enable-jumbo-apps has been added. This option increases the jobid and vpid field sizes to 32-bits. Someday, if necessary, someone can add yet another option to increase them to 64-bits, I suppose.
(b) replacing the string nodename with an integer nodeid. Since we have one daemon/node, the nodeid corresponds to the local daemon's vpid. This replaces an often lengthy string with only 2 (or at most 4) bytes, a substantial reduction.
(c) when the mca param requesting that nodenames be sent to support pretty error messages, a second mca param is now used to request FQDN - otherwise, the domain name is stripped (by default) from the message to save space. If someone wants to combine those into a single param somehow (perhaps with an argument?), they are welcome to do so - I didn't want to alter what people are already using.
While these may seem like small savings, they actually amount to a significant impact when aggregated across the entire modex operation. Since every proc must receive the modex data regardless of the collective used to send it, just reducing the size of the process name removes nearly 400MBytes of communication from a 32k proc job (admittedly, much of this comm may occur in parallel). So it does add up pretty quickly.
3. routing RML messages to reduce connections. The default messaging system remains point-to-point - i.e., each proc opens a socket to every proc it communicates with and sends its messages directly. A new option uses the orteds as routers - i.e., each proc only opens a single socket to its local orted. All messages are sent from the proc to the orted, which forwards the message to the orted on the node where the intended recipient proc is located - that orted then forwards the message to its local proc (the recipient). This greatly reduces the connection storm we have encountered during startup.
It also has the benefit of removing the sharing of every proc's OOB contact with every other proc. The orted routing tables are populated during launch since every orted gets a map of where every proc is being placed. Each proc, therefore, only needs to know the contact info for its local daemon, which is passed in via the environment when the proc is fork/exec'd by the daemon. This alone removes ~50 bytes/process of communication that was in the current STG1 startup message - so for our 32k proc job, this saves us roughly 32k*50 = 1.6MBytes sent to 32k procs = 51GBytes of messaging.
Note that you can use the new routing method by specifying -mca routed tree - if you so desire. This mode will become the default at some point in the future.
There are a few minor additional changes in the commit that I'll just note in passing:
* propagation of command line mca params to the orteds - fixes ticket #1073. See note there for details.
* requiring of "finalize" prior to "exit" for MPI procs - fixes ticket #1144. See note there for details.
* cleanup of some stale header files
This commit was SVN r16364.
2007-10-05 23:48:23 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
static void set_handler_default(int sig);
|
|
|
|
|
|
|
|
orte_odls_base_module_t orte_odls_default_module = {
|
2007-10-10 19:02:10 +04:00
|
|
|
orte_odls_base_default_get_add_procs_data,
|
2006-09-15 01:29:51 +04:00
|
|
|
orte_odls_default_launch_local_procs,
|
|
|
|
orte_odls_default_kill_local_procs,
|
Bring in the code for routing xcast stage gate messages via the local orteds. This code is inactive unless you specifically request it via an mca param oob_xcast_mode (can be set to "linear" or "direct"). Direct mode is the old standard method where we send messages directly to each MPI process. Linear mode sends the xcast message via the orteds, with the HNP sending the message to each orted directly.
There is a binomial algorithm in the code (i.e., the HNP would send to a subset of the orteds, which then relay it on according to the typical log-2 algo), but that has a bug in it so the code won't let you select it even if you tried (and the mca param doesn't show, so you'd *really* have to try).
This also involved a slight change to the oob.xcast API, so propagated that as required.
Note: this has *only* been tested on rsh, SLURM, and Bproc environments (now that it has been transferred to the OMPI trunk, I'll need to re-test it [only done rsh so far]). It should work fine on any environment that uses the ORTE daemons - anywhere else, you are on your own... :-)
Also, correct a mistake where the orte_debug_flag was declared an int, but the mca param was set as a bool. Move the storage for that flag to the orte/runtime/params.c and orte/runtime/params.h files appropriately.
This commit was SVN r14475.
2007-04-23 22:41:04 +04:00
|
|
|
orte_odls_default_signal_local_procs,
|
2007-10-10 19:02:10 +04:00
|
|
|
orte_odls_base_default_deliver_message,
|
2009-01-27 22:13:56 +03:00
|
|
|
orte_odls_base_default_require_sync
|
2006-09-15 01:29:51 +04:00
|
|
|
};
|
|
|
|
|
2009-09-18 23:48:42 +04:00
|
|
|
/* convenience macro for erroring out */
|
|
|
|
#define ORTE_ODLS_ERROR_OUT(errval) \
|
|
|
|
do { \
|
|
|
|
rc = (errval); \
|
|
|
|
write(p[1], &rc, sizeof(int)); \
|
|
|
|
exit(1); \
|
|
|
|
} while(0);
|
|
|
|
|
2009-09-19 21:43:21 +04:00
|
|
|
/* convenience macro for checking binding requirements */
|
|
|
|
#define ORTE_ODLS_IF_BIND_NOT_REQD(n) \
|
|
|
|
do { \
|
|
|
|
if (ORTE_BINDING_NOT_REQUIRED(jobdat->policy)) { \
|
|
|
|
if (orte_odls_globals.report_bindings) { \
|
|
|
|
orte_show_help("help-odls-default.txt", \
|
2009-09-21 17:22:37 +04:00
|
|
|
"odls-default:binding-not-avail", \
|
2009-09-19 21:43:21 +04:00
|
|
|
true, (n)); \
|
|
|
|
} \
|
|
|
|
goto LAUNCH_PROCS; \
|
|
|
|
} \
|
|
|
|
} while(0);
|
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
static bool odls_default_child_died(pid_t pid, unsigned int timeout, int *exit_status)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
|
|
|
time_t end;
|
|
|
|
pid_t ret;
|
2006-11-13 21:51:18 +03:00
|
|
|
#if !defined(HAVE_SCHED_YIELD)
|
|
|
|
struct timeval t;
|
|
|
|
fd_set bogus;
|
|
|
|
#endif
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
end = time(NULL) + timeout;
|
|
|
|
do {
|
|
|
|
ret = waitpid(pid, exit_status, WNOHANG);
|
|
|
|
if (pid == ret) {
|
|
|
|
/* It died -- return success */
|
|
|
|
return true;
|
2008-02-28 04:57:57 +03:00
|
|
|
} else if (0 == ret) {
|
|
|
|
/* with NOHANG specified, if a process has already exited
|
|
|
|
* while waitpid was registered, then waitpid returns 0
|
|
|
|
* as there is no error - this is a race condition problem
|
|
|
|
* that occasionally causes us to incorrectly report a proc
|
|
|
|
* as refusing to die. Unfortunately, errno may not be reset
|
|
|
|
* by waitpid in this case, so we cannot check it - just assume
|
|
|
|
* the proc has indeed died
|
|
|
|
*/
|
|
|
|
return true;
|
2006-09-15 01:29:51 +04:00
|
|
|
} else if (-1 == ret && ECHILD == errno) {
|
|
|
|
/* The pid no longer exists, so we'll call this "good
|
|
|
|
enough for government work" */
|
|
|
|
return true;
|
|
|
|
}
|
2008-02-28 04:57:57 +03:00
|
|
|
|
2006-11-13 21:51:18 +03:00
|
|
|
#if defined(HAVE_SCHED_YIELD)
|
2006-11-13 15:45:03 +03:00
|
|
|
sched_yield();
|
2006-11-13 21:51:18 +03:00
|
|
|
#else
|
|
|
|
/* Bogus delay for 1 usec */
|
|
|
|
t.tv_sec = 0;
|
|
|
|
t.tv_usec = 1;
|
|
|
|
FD_ZERO(&bogus);
|
|
|
|
FD_SET(0, &bogus);
|
|
|
|
select(1, &bogus, NULL, NULL, &t);
|
2006-11-13 15:45:03 +03:00
|
|
|
#endif
|
2006-11-13 21:51:18 +03:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
} while (time(NULL) < end);
|
|
|
|
|
|
|
|
/* The child didn't die, so return false */
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
static int odls_default_kill_local(pid_t pid, int signum)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
2007-10-10 19:02:10 +04:00
|
|
|
if (0 != kill(pid, signum)) {
|
|
|
|
if (ESRCH != errno) return errno;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2007-10-10 19:02:10 +04:00
|
|
|
return 0;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
|
|
|
|
2009-07-13 06:29:17 +04:00
|
|
|
int orte_odls_default_kill_local_procs(opal_pointer_array_t *procs, bool set_state)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
|
|
|
int rc;
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 22:34:59 +03:00
|
|
|
|
2009-07-13 06:29:17 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_odls_base_default_kill_local_procs(procs, set_state,
|
2007-10-10 19:02:10 +04:00
|
|
|
odls_default_kill_local, odls_default_child_died))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
2007-10-10 19:02:10 +04:00
|
|
|
return rc;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2007-10-10 19:02:10 +04:00
|
|
|
return ORTE_SUCCESS;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Fork/exec the specified processes
|
|
|
|
*/
|
|
|
|
|
2008-08-13 21:47:24 +04:00
|
|
|
static int odls_default_fork_local_proc(orte_app_context_t* context,
|
|
|
|
orte_odls_child_t *child,
|
|
|
|
char **environ_copy,
|
2009-08-11 06:51:27 +04:00
|
|
|
orte_odls_job_t *jobdat)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
|
|
|
orte_iof_base_io_conf_t opts;
|
|
|
|
int rc;
|
|
|
|
sigset_t sigs;
|
2007-10-10 19:02:10 +04:00
|
|
|
int i, p[2];
|
2008-08-13 21:47:24 +04:00
|
|
|
pid_t pid;
|
2009-05-12 06:18:35 +04:00
|
|
|
bool paffinity_enabled = false;
|
2009-08-11 06:51:27 +04:00
|
|
|
opal_paffinity_base_cpu_set_t mask;
|
|
|
|
orte_node_rank_t nrank;
|
|
|
|
int16_t n;
|
|
|
|
orte_local_rank_t lrank;
|
2009-08-19 23:29:15 +04:00
|
|
|
int target_socket, npersocket, logical_skt;
|
|
|
|
int logical_cpu, phys_core, phys_cpu, ncpu;
|
|
|
|
bool bound = false;
|
2009-08-11 06:51:27 +04:00
|
|
|
|
2008-08-13 21:47:24 +04:00
|
|
|
if (NULL != child) {
|
|
|
|
/* should pull this information from MPIRUN instead of going with
|
|
|
|
default */
|
2009-05-07 00:11:28 +04:00
|
|
|
opts.usepty = OPAL_ENABLE_PTY_SUPPORT;
|
2008-08-13 21:47:24 +04:00
|
|
|
|
Roll in the revamped IOF subsystem. Per the devel mailing list email, this is a complete rewrite of the iof framework designed to simplify the code for maintainability, and to support features we had planned to do, but were too difficult to implement in the old code. Specifically, the new code:
1. completely and cleanly separates responsibilities between the HNP, orted, and tool components.
2. removes all wireup messaging during launch and shutdown.
3. maintains flow control for stdin to avoid large-scale consumption of memory by orteds when large input files are forwarded. This is done using an xon/xoff protocol.
4. enables specification of stdin recipients on the mpirun cmd line. Allowed options include rank, "all", or "none". Default is rank 0.
5. creates a new MPI_Info key "ompi_stdin_target" that supports the above options for child jobs. Default is "none".
6. adds a new tool "orte-iof" that can connect to a running mpirun and display the output. Cmd line options allow selection of any combination of stdout, stderr, and stddiag. Default is stdout.
7. adds a new mpirun and orte-iof cmd line option "tag-output" that will tag each line of output with process name and stream ident. For example, "[1,0]<stdout>this is output"
This is not intended for the 1.3 release as it is a major change requiring considerable soak time.
This commit was SVN r19767.
2008-10-18 04:00:49 +04:00
|
|
|
/* do we want to setup stdin? */
|
|
|
|
if (NULL != child &&
|
2009-08-11 06:51:27 +04:00
|
|
|
(jobdat->stdin_target == ORTE_VPID_WILDCARD || child->name->vpid == jobdat->stdin_target)) {
|
2008-08-13 21:47:24 +04:00
|
|
|
opts.connect_stdin = true;
|
|
|
|
} else {
|
|
|
|
opts.connect_stdin = false;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_iof_base_setup_prefork(&opts))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
if (NULL != child) {
|
|
|
|
child->state = ORTE_PROC_STATE_FAILED_TO_START;
|
|
|
|
child->exit_code = rc;
|
|
|
|
}
|
|
|
|
return rc;
|
|
|
|
}
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2007-04-24 22:54:45 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* A pipe is used to communicate between the parent and child to
|
2009-09-18 23:48:42 +04:00
|
|
|
indicate whether the exec ultimately succeeded or failed. The
|
|
|
|
child sets the pipe to be close-on-exec; the child only ever
|
|
|
|
writes anything to the pipe if there is an error (e.g.,
|
|
|
|
executable not found, exec() fails, etc.). The parent does a
|
|
|
|
blocking read on the pipe; if the pipe closed with no data,
|
|
|
|
then the exec() succeeded. If the parent reads something from
|
|
|
|
the pipe, then the child was letting us know that it failed. */
|
2006-09-15 01:29:51 +04:00
|
|
|
if (pipe(p) < 0) {
|
2007-04-24 22:54:45 +04:00
|
|
|
ORTE_ERROR_LOG(ORTE_ERR_SYS_LIMITS_PIPES);
|
2008-08-13 21:47:24 +04:00
|
|
|
if (NULL != child) {
|
|
|
|
child->state = ORTE_PROC_STATE_FAILED_TO_START;
|
|
|
|
child->exit_code = ORTE_ERR_SYS_LIMITS_PIPES;
|
|
|
|
}
|
2007-04-24 22:54:45 +04:00
|
|
|
return ORTE_ERR_SYS_LIMITS_PIPES;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* Fork off the child */
|
2008-08-13 21:47:24 +04:00
|
|
|
pid = fork();
|
|
|
|
if (NULL != child) {
|
|
|
|
child->pid = pid;
|
|
|
|
}
|
|
|
|
|
|
|
|
if(pid < 0) {
|
2007-04-24 22:54:45 +04:00
|
|
|
ORTE_ERROR_LOG(ORTE_ERR_SYS_LIMITS_CHILDREN);
|
2008-08-13 21:47:24 +04:00
|
|
|
if (NULL != child) {
|
|
|
|
child->state = ORTE_PROC_STATE_FAILED_TO_START;
|
|
|
|
child->exit_code = ORTE_ERR_SYS_LIMITS_CHILDREN;
|
|
|
|
}
|
2007-04-24 22:54:45 +04:00
|
|
|
return ORTE_ERR_SYS_LIMITS_CHILDREN;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2008-08-13 21:47:24 +04:00
|
|
|
if (pid == 0) {
|
2006-09-15 01:29:51 +04:00
|
|
|
long fd, fdmax = sysconf(_SC_OPEN_MAX);
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* Setup the pipe to be close-on-exec */
|
|
|
|
close(p[0]);
|
|
|
|
fcntl(p[1], F_SETFD, FD_CLOEXEC);
|
2009-09-18 23:48:42 +04:00
|
|
|
|
|
|
|
if (NULL != child) {
|
2008-08-13 21:47:24 +04:00
|
|
|
/* setup stdout/stderr so that any error messages that we may
|
|
|
|
print out will get displayed back at orterun.
|
|
|
|
|
|
|
|
NOTE: Definitely do this AFTER we check contexts so that any
|
|
|
|
error message from those two functions doesn't come out to the
|
|
|
|
user. IF we didn't do it in this order, THEN a user who gives
|
|
|
|
us a bad executable name or working directory would get N
|
|
|
|
error messages, where N=num_procs. This would be very annoying
|
|
|
|
for large jobs, so instead we set things up so that orterun
|
|
|
|
always outputs a nice, single message indicating what happened
|
|
|
|
*/
|
2009-09-18 23:48:42 +04:00
|
|
|
if (ORTE_SUCCESS != (i = orte_iof_base_setup_child(&opts, &environ_copy))) {
|
|
|
|
ORTE_ODLS_ERROR_OUT(i);
|
2008-08-13 21:47:24 +04:00
|
|
|
}
|
2009-09-18 23:48:42 +04:00
|
|
|
|
|
|
|
/* Setup process affinity. First check to see if a slot list was
|
|
|
|
* specified. If so, use it. If no slot list was specified,
|
|
|
|
* that's not an error -- just fall through and try the next
|
|
|
|
* paffinity scheme.
|
|
|
|
*/
|
|
|
|
if (NULL != child->slot_list) {
|
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
|
|
|
"%s odls:default:fork got slot_list %s for child %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
child->slot_list, ORTE_NAME_PRINT(child->name)));
|
|
|
|
if (opal_paffinity_alone) {
|
|
|
|
/* It's an error if multiple paffinity schemes were specified */
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:multiple-paffinity-schemes", true, child->slot_list);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
if (orte_odls_globals.report_bindings) {
|
|
|
|
opal_output(0, "%s odls:default:fork binding child %s to slot_list %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_NAME_PRINT(child->name), child->slot_list);
|
|
|
|
}
|
|
|
|
if (ORTE_SUCCESS != (rc = opal_paffinity_base_slot_list_set((long)child->name->vpid, child->slot_list))) {
|
|
|
|
if (ORTE_ERR_NOT_SUPPORTED == rc) {
|
|
|
|
/* OS doesn't support providing topology information */
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:topo-not-supported",
|
|
|
|
true, orte_process_info.nodename, "rankfile containing a slot_list of ",
|
|
|
|
child->slot_list, context->app);
|
|
|
|
ORTE_ODLS_ERROR_OUT(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:slot-list-failed", true, child->slot_list, ORTE_ERROR_NAME(rc));
|
|
|
|
ORTE_ODLS_ERROR_OUT(rc);
|
|
|
|
}
|
|
|
|
} else if (ORTE_BIND_TO_CORE & jobdat->policy) {
|
|
|
|
/* we want to bind this proc to a specific core, or multiple cores
|
|
|
|
* if the cpus_per_rank is > 0
|
|
|
|
*/
|
|
|
|
OPAL_OUTPUT_VERBOSE((5, orte_odls_globals.output,
|
|
|
|
"%s odls:default:fork binding child %s to core(s) cpus/rank %d stride %d",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_NAME_PRINT(child->name),
|
|
|
|
(int)jobdat->cpus_per_rank, (int)jobdat->stride));
|
|
|
|
/* get the node rank */
|
|
|
|
if (ORTE_NODE_RANK_INVALID == (nrank = orte_ess.get_node_rank(child->name))) {
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:invalid-node-rank", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
OPAL_PAFFINITY_CPU_ZERO(mask);
|
|
|
|
if (ORTE_MAPPING_NPERXXX & jobdat->policy) {
|
|
|
|
/* if npersocket was set, then we divide the number of cores
|
|
|
|
* per socket by the #localprocs/#sockets to determine how many cores
|
|
|
|
* each rank gets
|
|
|
|
*/
|
|
|
|
npersocket = jobdat->num_local_procs / orte_odls_globals.num_sockets;
|
|
|
|
/* compute the #cores/process */
|
|
|
|
jobdat->cpus_per_rank = orte_default_num_cores_per_socket / npersocket;
|
|
|
|
/* figure out which logical cpu this node rank should start on as we
|
|
|
|
* must ensure it starts on the right socket
|
|
|
|
*/
|
|
|
|
logical_cpu = (nrank / npersocket) * orte_default_num_cores_per_socket;
|
|
|
|
/* now add an offset within the socket */
|
|
|
|
logical_cpu += (nrank % npersocket) * jobdat->cpus_per_rank;
|
|
|
|
} else {
|
|
|
|
/* my starting core has to be offset by cpus_per_rank */
|
|
|
|
logical_cpu = nrank * jobdat->cpus_per_rank;
|
|
|
|
}
|
|
|
|
for (n=0; n < jobdat->cpus_per_rank; n++) {
|
|
|
|
/* are we bound? */
|
|
|
|
if (orte_odls_globals.bound) {
|
|
|
|
/* if we are bound, then use the logical_cpu as an index
|
|
|
|
* against our available cores
|
|
|
|
*/
|
|
|
|
ncpu = 0;
|
|
|
|
for (i=0; i < orte_odls_globals.num_processors && ncpu <= logical_cpu; i++) {
|
|
|
|
if (OPAL_PAFFINITY_CPU_ISSET(i, orte_odls_globals.my_cores)) {
|
|
|
|
ncpu++;
|
|
|
|
phys_cpu = i;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* if we don't have enough processors, that is an error */
|
|
|
|
if (ncpu < logical_cpu) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-core");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:not-enough-processors", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
/* if we are not bound, then all processors are available
|
|
|
|
* to us, so index into the node's array to get the
|
|
|
|
* physical cpu
|
|
|
|
*/
|
|
|
|
phys_cpu = opal_paffinity_base_get_physical_processor_id(logical_cpu);
|
|
|
|
if (0 > phys_cpu) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-core");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:invalid-phys-cpu", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
OPAL_PAFFINITY_CPU_SET(phys_cpu, mask);
|
|
|
|
logical_cpu += jobdat->stride;
|
|
|
|
}
|
|
|
|
if (orte_odls_globals.report_bindings) {
|
|
|
|
opal_output(0, "%s odls:default:fork binding child %s to cpus %04lx",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_NAME_PRINT(child->name), mask.bitmask[0]);
|
|
|
|
}
|
|
|
|
if (ORTE_SUCCESS != (rc = opal_paffinity_base_set(mask))) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-core");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:failed-set-paff", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(rc);
|
|
|
|
}
|
|
|
|
paffinity_enabled = true;
|
|
|
|
} else if (ORTE_BIND_TO_SOCKET & jobdat->policy) {
|
|
|
|
/* bind this proc to a socket */
|
|
|
|
OPAL_OUTPUT_VERBOSE((5, orte_odls_globals.output,
|
|
|
|
"%s odls:default:fork binding child %s to socket",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_NAME_PRINT(child->name)));
|
|
|
|
/* layout this process across the sockets based on
|
|
|
|
* the provided mapping policy
|
|
|
|
*/
|
|
|
|
if (ORTE_LOCAL_RANK_INVALID == (lrank = orte_ess.get_local_rank(child->name))) {
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:invalid-local-rank", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
if (ORTE_MAPPING_NPERXXX & jobdat->policy) {
|
|
|
|
/* we need to balance the children from this job across the available sockets */
|
|
|
|
npersocket = jobdat->num_local_procs / orte_odls_globals.num_sockets;
|
|
|
|
/* determine the socket to use based on those available */
|
|
|
|
if (npersocket < 2) {
|
|
|
|
/* if we only have 1/sock, or we have less procs than sockets,
|
|
|
|
* then just put it on the lrank socket
|
|
|
|
*/
|
|
|
|
logical_skt = lrank;
|
|
|
|
} else if (ORTE_MAPPING_BYSOCKET & jobdat->policy) {
|
|
|
|
logical_skt = lrank % npersocket;
|
|
|
|
} else {
|
|
|
|
logical_skt = lrank / npersocket;
|
|
|
|
}
|
|
|
|
if (orte_odls_globals.bound) {
|
|
|
|
/* if we are bound, use this as an index into our available sockets */
|
|
|
|
for (target_socket=0; target_socket < opal_bitmap_size(&orte_odls_globals.sockets) && n < logical_skt; target_socket++) {
|
|
|
|
if (opal_bitmap_is_set_bit(&orte_odls_globals.sockets, target_socket)) {
|
|
|
|
n++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* if we don't have enough sockets, that is an error */
|
|
|
|
if (n < logical_skt) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:not-enough-sockets", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
target_socket = opal_paffinity_base_get_physical_socket_id(logical_skt);
|
|
|
|
if (ORTE_ERR_NOT_SUPPORTED == target_socket) {
|
|
|
|
/* OS doesn't support providing topology information */
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:topo-not-supported",
|
|
|
|
true, orte_process_info.nodename, "bind-to-socket", "",
|
|
|
|
context->app);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
|
|
|
"%s odls:default:fork child %s local rank %d npersocket %d logical socket %d target socket %d",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME), ORTE_NAME_PRINT(child->name), lrank,
|
|
|
|
npersocket, logical_skt, target_socket));
|
|
|
|
} else if (ORTE_MAPPING_BYSOCKET & jobdat->policy) {
|
|
|
|
/* this corresponds to a mapping policy where
|
|
|
|
* local rank 0 goes on socket 0, and local
|
|
|
|
* rank 1 goes on socket 1, etc. - round robin
|
|
|
|
* until all ranks are mapped
|
|
|
|
*
|
|
|
|
* NOTE: we already know our number of sockets
|
|
|
|
* from when we initialized
|
|
|
|
*/
|
|
|
|
target_socket = opal_paffinity_base_get_physical_socket_id(lrank % orte_odls_globals.num_sockets);
|
|
|
|
if (ORTE_ERR_NOT_SUPPORTED == target_socket) {
|
|
|
|
/* OS does not support providing topology information */
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:topo-not-supported",
|
|
|
|
true, orte_process_info.nodename, "bind-to-socket", "",
|
|
|
|
context->app);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
|
|
|
"bysocket lrank %d numsocks %d logical socket %d target socket %d", (int)lrank,
|
|
|
|
(int)orte_odls_globals.num_sockets,
|
|
|
|
(int)(lrank % orte_odls_globals.num_sockets),
|
|
|
|
target_socket));
|
|
|
|
} else {
|
|
|
|
/* use a byslot-like policy where local rank 0 goes on
|
|
|
|
* socket 0, and local rank 1 goes on socket 0, etc.
|
|
|
|
* following round-robin until all ranks mapped
|
|
|
|
*/
|
|
|
|
if (orte_odls_globals.bound) {
|
|
|
|
/* if we are bound, then we compute the logical socket id
|
|
|
|
* based on the number of available cores in each socket so
|
|
|
|
* that each rank gets its own core, adjusting for the cpus_per_task
|
|
|
|
*/
|
|
|
|
/* Find the lrank available core, accounting for cpus_per_task */
|
|
|
|
logical_cpu = lrank * jobdat->cpus_per_rank;
|
|
|
|
/* use the logical_cpu as an index against our available cores */
|
|
|
|
ncpu = 0;
|
|
|
|
for (i=0; i < orte_odls_globals.num_processors && ncpu <= logical_cpu; i++) {
|
|
|
|
if (OPAL_PAFFINITY_CPU_ISSET(i, orte_odls_globals.my_cores)) {
|
|
|
|
ncpu++;
|
|
|
|
phys_cpu = i;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* if we don't have enough processors, that is an error */
|
|
|
|
if (ncpu < logical_cpu) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:not-enough-processors", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
/* get the physical socket of that cpu */
|
|
|
|
if (ORTE_SUCCESS != opal_paffinity_base_get_map_to_socket_core(phys_cpu, &target_socket, &phys_core)) {
|
|
|
|
if (ORTE_BINDING_NOT_REQUIRED(jobdat->policy)) {
|
|
|
|
goto LAUNCH_PROCS;
|
|
|
|
}
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:not-enough-sockets", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
/* if we are not bound, then just use all sockets */
|
|
|
|
if (1 == orte_odls_globals.num_sockets) {
|
|
|
|
/* if we only have one socket, then just put it there */
|
|
|
|
target_socket = opal_paffinity_base_get_physical_socket_id(0);
|
|
|
|
if (ORTE_ERR_NOT_SUPPORTED == target_socket) {
|
|
|
|
/* OS doesn't support providing topology information */
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:topo-not-supported",
|
|
|
|
true, orte_process_info.nodename, "bind-to-socket", "",
|
|
|
|
context->app);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
/* compute the logical socket, compensating for the number of cpus_per_rank */
|
|
|
|
logical_skt = lrank / (orte_default_num_cores_per_socket / jobdat->cpus_per_rank);
|
|
|
|
/* wrap that around the number of sockets so we round-robin */
|
|
|
|
logical_skt = logical_skt % orte_odls_globals.num_sockets;
|
|
|
|
/* now get the target physical socket */
|
|
|
|
target_socket = opal_paffinity_base_get_physical_socket_id(logical_skt);
|
|
|
|
if (ORTE_ERR_NOT_SUPPORTED == target_socket) {
|
|
|
|
/* OS doesn't support providing topology information */
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:topo-not-supported",
|
|
|
|
true, orte_process_info.nodename, "bind-to-socket", "",
|
|
|
|
context->app);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
|
|
|
"byslot lrank %d socket %d", (int)lrank, target_socket));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
OPAL_PAFFINITY_CPU_ZERO(mask);
|
|
|
|
|
|
|
|
for (n=0; n < orte_default_num_cores_per_socket; n++) {
|
|
|
|
/* get the physical core within this target socket */
|
|
|
|
phys_core = opal_paffinity_base_get_physical_core_id(target_socket, n);
|
|
|
|
if (0 > phys_core) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:invalid-phys-cpu", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
/* map this to a physical cpu on this node */
|
|
|
|
if (ORTE_SUCCESS != opal_paffinity_base_get_map_to_processor_id(target_socket, phys_core, &phys_cpu)) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:invalid-phys-cpu", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
/* are we bound? */
|
|
|
|
if (orte_odls_globals.bound) {
|
|
|
|
/* see if this physical cpu is available to us */
|
|
|
|
if (!OPAL_PAFFINITY_CPU_ISSET(phys_cpu, orte_odls_globals.my_cores)) {
|
|
|
|
/* no it isn't - skip it */
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
|
|
|
"%s odls:default:fork mapping phys socket %d core %d to phys_cpu %d",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
target_socket, phys_core, phys_cpu));
|
|
|
|
OPAL_PAFFINITY_CPU_SET(phys_cpu, mask);
|
|
|
|
}
|
|
|
|
/* if we did not bind it anywhere, then that is an error */
|
|
|
|
OPAL_PAFFINITY_PROCESS_IS_BOUND(mask, &bound);
|
|
|
|
if (!bound) {
|
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:could-not-bind-to-socket", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(ORTE_ERR_FATAL);
|
|
|
|
}
|
|
|
|
if (orte_odls_globals.report_bindings) {
|
|
|
|
opal_output(0, "%s odls:default:fork binding child %s to socket %d cpus %04lx",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_NAME_PRINT(child->name), target_socket, mask.bitmask[0]);
|
|
|
|
}
|
|
|
|
if (ORTE_SUCCESS != (rc = opal_paffinity_base_set(mask))) {
|
2009-09-19 21:43:21 +04:00
|
|
|
ORTE_ODLS_IF_BIND_NOT_REQD("bind-to-socket");
|
2009-09-18 23:48:42 +04:00
|
|
|
orte_show_help("help-odls-default.txt",
|
|
|
|
"odls-default:failed-set-paff", true);
|
|
|
|
ORTE_ODLS_ERROR_OUT(rc);
|
|
|
|
}
|
|
|
|
paffinity_enabled = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If we were able to set processor affinity, try setting up
|
|
|
|
* memory affinity
|
|
|
|
*/
|
|
|
|
if (paffinity_enabled) {
|
|
|
|
if (OPAL_SUCCESS == opal_maffinity_base_open() &&
|
|
|
|
OPAL_SUCCESS == opal_maffinity_base_select()) {
|
|
|
|
opal_maffinity_setup = true;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
} else if (!(ORTE_JOB_CONTROL_FORWARD_OUTPUT & jobdat->controls)) {
|
|
|
|
/* tie stdin/out/err/internal to /dev/null */
|
|
|
|
int fdnull;
|
|
|
|
for (i=0; i < 3; i++) {
|
|
|
|
fdnull = open("/dev/null", O_RDONLY, 0);
|
|
|
|
if(fdnull > i) {
|
|
|
|
dup2(fdnull, i);
|
|
|
|
}
|
|
|
|
close(fdnull);
|
2008-08-13 21:47:24 +04:00
|
|
|
}
|
|
|
|
fdnull = open("/dev/null", O_RDONLY, 0);
|
|
|
|
if(fdnull > opts.p_internal[1]) {
|
|
|
|
dup2(fdnull, opts.p_internal[1]);
|
|
|
|
}
|
2008-10-31 21:05:28 +03:00
|
|
|
close(fdnull);
|
2007-04-24 22:54:45 +04:00
|
|
|
}
|
2009-09-18 23:48:42 +04:00
|
|
|
|
|
|
|
LAUNCH_PROCS:
|
2008-06-09 18:53:58 +04:00
|
|
|
/* close all file descriptors w/ exception of
|
2008-08-13 21:47:24 +04:00
|
|
|
* stdin/stdout/stderr and the pipe used for the IOF INTERNAL
|
|
|
|
* messages
|
|
|
|
*/
|
2008-06-09 18:53:58 +04:00
|
|
|
for(fd=3; fd<fdmax; fd++) {
|
|
|
|
if (fd != opts.p_internal[1]) {
|
|
|
|
close(fd);
|
|
|
|
}
|
|
|
|
}
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
if (context->argv == NULL) {
|
|
|
|
context->argv = malloc(sizeof(char*)*2);
|
|
|
|
context->argv[0] = strdup(context->app);
|
|
|
|
context->argv[1] = NULL;
|
|
|
|
}
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* Set signal handlers back to the default. Do this close to
|
2009-09-18 23:48:42 +04:00
|
|
|
the exev() because the event library may (and likely will)
|
|
|
|
reset them. If we don't do this, the event library may
|
|
|
|
have left some set that, at least on some OS's, don't get
|
|
|
|
reset via fork() or exec(). Hence, the launched process
|
|
|
|
could be unkillable (for example). */
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
set_handler_default(SIGTERM);
|
|
|
|
set_handler_default(SIGINT);
|
|
|
|
set_handler_default(SIGHUP);
|
|
|
|
set_handler_default(SIGPIPE);
|
|
|
|
set_handler_default(SIGCHLD);
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* Unblock all signals, for many of the same reasons that we
|
2009-09-18 23:48:42 +04:00
|
|
|
set the default handlers, above. This is noticable on
|
|
|
|
Linux where the event library blocks SIGTERM, but we don't
|
|
|
|
want that blocked by the launched process. */
|
2006-09-15 01:29:51 +04:00
|
|
|
sigprocmask(0, 0, &sigs);
|
|
|
|
sigprocmask(SIG_UNBLOCK, &sigs, 0);
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* Exec the new executable */
|
2009-09-18 23:48:42 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
execve(context->app, context->argv, environ_copy);
|
This commit represents a bunch of work on a Mercurial side branch. As
such, the commit message back to the master SVN repository is fairly
long.
= ORTE Job-Level Output Messages =
Add two new interfaces that should be used for all new code throughout
the ORTE and OMPI layers (we already make the search-and-replace on
the existing ORTE / OMPI layers):
* orte_output(): (and corresponding friends ORTE_OUTPUT,
orte_output_verbose, etc.) This function sends the output directly
to the HNP for processing as part of a job-specific output
channel. It supports all the same outputs as opal_output()
(syslog, file, stdout, stderr), but for stdout/stderr, the output
is sent to the HNP for processing and output. More on this below.
* orte_show_help(): This function is a drop-in-replacement for
opal_show_help(), with two differences in functionality:
1. the rendered text help message output is sent to the HNP for
display (rather than outputting directly into the process' stderr
stream)
1. the HNP detects duplicate help messages and does not display them
(so that you don't see the same error message N times, once from
each of your N MPI processes); instead, it counts "new" instances
of the help message and displays a message every ~5 seconds when
there are new ones ("I got X new copies of the help message...")
opal_show_help and opal_output still exist, but they only output in
the current process. The intent for the new orte_* functions is that
they can apply job-level intelligence to the output. As such, we
recommend that all new ORTE and OMPI code use the new orte_*
functions, not thei opal_* functions.
=== New code ===
For ORTE and OMPI programmers, here's what you need to do differently
in new code:
* Do not include opal/util/show_help.h or opal/util/output.h.
Instead, include orte/util/output.h (this one header file has
declarations for both the orte_output() series of functions and
orte_show_help()).
* Effectively s/opal_output/orte_output/gi throughout your code.
Note that orte_output_open() takes a slightly different argument
list (as a way to pass data to the filtering stream -- see below),
so you if explicitly call opal_output_open(), you'll need to
slightly adapt to the new signature of orte_output_open().
* Literally s/opal_show_help/orte_show_help/. The function signature
is identical.
=== Notes ===
* orte_output'ing to stream 0 will do similar to what
opal_output'ing did, so leaving a hard-coded "0" as the first
argument is safe.
* For systems that do not use ORTE's RML or the HNP, the effect of
orte_output_* and orte_show_help will be identical to their opal
counterparts (the additional information passed to
orte_output_open() will be lost!). Indeed, the orte_* functions
simply become trivial wrappers to their opal_* counterparts. Note
that we have not tested this; the code is simple but it is quite
possible that we mucked something up.
= Filter Framework =
Messages sent view the new orte_* functions described above and
messages output via the IOF on the HNP will now optionally be passed
through a new "filter" framework before being output to
stdout/stderr. The "filter" OPAL MCA framework is intended to allow
preprocessing to messages before they are sent to their final
destinations. The first component that was written in the filter
framework was to create an XML stream, segregating all the messages
into different XML tags, etc. This will allow 3rd party tools to read
the stdout/stderr from the HNP and be able to know exactly what each
text message is (e.g., a help message, another OMPI infrastructure
message, stdout from the user process, stderr from the user process,
etc.).
Filtering is not active by default. Filter components must be
specifically requested, such as:
{{{
$ mpirun --mca filter xml ...
}}}
There can only be one filter component active.
= New MCA Parameters =
The new functionality described above introduces two new MCA
parameters:
* '''orte_base_help_aggregate''': Defaults to 1 (true), meaning that
help messages will be aggregated, as described above. If set to 0,
all help messages will be displayed, even if they are duplicates
(i.e., the original behavior).
* '''orte_base_show_output_recursions''': An MCA parameter to help
debug one of the known issues, described below. It is likely that
this MCA parameter will disappear before v1.3 final.
= Known Issues =
* The XML filter component is not complete. The current output from
this component is preliminary and not real XML. A bit more work
needs to be done to configure.m4 search for an appropriate XML
library/link it in/use it at run time.
* There are possible recursion loops in the orte_output() and
orte_show_help() functions -- e.g., if RML send calls orte_output()
or orte_show_help(). We have some ideas how to fix these, but
figured that it was ok to commit before feature freeze with known
issues. The code currently contains sub-optimal workarounds so
that this will not be a problem, but it would be good to actually
solve the problem rather than have hackish workarounds before v1.3 final.
This commit was SVN r18434.
2008-05-14 00:00:55 +04:00
|
|
|
orte_show_help("help-odls-default.txt", "orte-odls-default:execv-error",
|
2006-09-15 01:29:51 +04:00
|
|
|
true, context->app, strerror(errno));
|
2006-12-18 05:30:05 +03:00
|
|
|
exit(1);
|
2006-09-15 01:29:51 +04:00
|
|
|
} else {
|
|
|
|
|
2009-08-11 06:51:27 +04:00
|
|
|
if (NULL != child && (ORTE_JOB_CONTROL_FORWARD_OUTPUT & jobdat->controls)) {
|
2008-08-13 21:47:24 +04:00
|
|
|
/* connect endpoints IOF */
|
|
|
|
rc = orte_iof_base_setup_parent(child->name, &opts);
|
|
|
|
if(ORTE_SUCCESS != rc) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
return rc;
|
|
|
|
}
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Wait to read something from the pipe or close */
|
|
|
|
close(p[1]);
|
|
|
|
while (1) {
|
|
|
|
rc = read(p[0], &i, sizeof(int));
|
|
|
|
if (rc < 0) {
|
|
|
|
/* Signal interrupts are ok */
|
|
|
|
if (errno == EINTR) {
|
|
|
|
continue;
|
|
|
|
}
|
2008-08-13 21:47:24 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* Other errno's are bad */
|
2008-08-13 21:47:24 +04:00
|
|
|
if (NULL != child) {
|
|
|
|
child->state = ORTE_PROC_STATE_FAILED_TO_START;
|
|
|
|
child->exit_code = ORTE_ERR_PIPE_READ_FAILURE;
|
|
|
|
}
|
2008-02-28 04:57:57 +03:00
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s odls:default:fork got code %d back from child",
|
2009-03-06 00:50:47 +03:00
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME), i));
|
2008-10-31 21:05:28 +03:00
|
|
|
close(p[0]);
|
2007-04-24 22:54:45 +04:00
|
|
|
return ORTE_ERR_PIPE_READ_FAILURE;
|
2006-09-15 01:29:51 +04:00
|
|
|
} else if (0 == rc) {
|
|
|
|
/* Child was successful in exec'ing! */
|
|
|
|
break;
|
|
|
|
} else {
|
2007-04-24 22:54:45 +04:00
|
|
|
/* Doh -- child failed.
|
|
|
|
Let the calling function
|
|
|
|
know about the failure. The actual exit status of child proc
|
|
|
|
cannot be found here - all we can do is report the ORTE error
|
|
|
|
code that was reported back to us. The calling func needs to report the
|
|
|
|
failure to launch this process through the SMR or else
|
|
|
|
everyone else will hang.
|
2006-09-15 01:29:51 +04:00
|
|
|
*/
|
2008-08-13 21:47:24 +04:00
|
|
|
if (NULL != child) {
|
|
|
|
child->state = ORTE_PROC_STATE_FAILED_TO_START;
|
|
|
|
child->exit_code = i;
|
|
|
|
}
|
2008-02-28 04:57:57 +03:00
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s odls:default:fork got code %d back from child",
|
2009-03-06 00:50:47 +03:00
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME), i));
|
2008-10-31 21:05:28 +03:00
|
|
|
close(p[0]);
|
2009-08-11 06:51:27 +04:00
|
|
|
return ORTE_ERR_FAILED_TO_START;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2008-08-13 21:47:24 +04:00
|
|
|
if (NULL != child) {
|
|
|
|
/* set the proc state to LAUNCHED */
|
|
|
|
child->state = ORTE_PROC_STATE_LAUNCHED;
|
|
|
|
child->alive = true;
|
|
|
|
}
|
2008-10-31 21:05:28 +03:00
|
|
|
close(p[0]);
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2006-11-11 07:03:45 +03:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
return ORTE_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Launch all processes allocated to the current node.
|
|
|
|
*/
|
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
int orte_odls_default_launch_local_procs(opal_buffer_t *data)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
orte_jobid_t job;
|
2007-06-18 19:39:04 +04:00
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
/* construct the list of children we are to launch */
|
2008-04-30 23:49:53 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_odls_base_default_construct_child_list(data, &job))) {
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s odls:default:launch:local failed to construct child list on error %s",
|
2009-03-06 00:50:47 +03:00
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME), ORTE_ERROR_NAME(rc)));
|
2007-10-10 19:02:10 +04:00
|
|
|
goto CLEANUP;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2007-10-10 19:02:10 +04:00
|
|
|
|
|
|
|
/* launch the local procs */
|
2008-04-30 23:49:53 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_odls_base_default_launch_local(job, odls_default_fork_local_proc))) {
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((2, orte_odls_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s odls:default:launch:local failed to launch on error %s",
|
2009-03-06 00:50:47 +03:00
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME), ORTE_ERROR_NAME(rc)));
|
2007-10-10 19:02:10 +04:00
|
|
|
goto CLEANUP;
|
Bring in the code for routing xcast stage gate messages via the local orteds. This code is inactive unless you specifically request it via an mca param oob_xcast_mode (can be set to "linear" or "direct"). Direct mode is the old standard method where we send messages directly to each MPI process. Linear mode sends the xcast message via the orteds, with the HNP sending the message to each orted directly.
There is a binomial algorithm in the code (i.e., the HNP would send to a subset of the orteds, which then relay it on according to the typical log-2 algo), but that has a bug in it so the code won't let you select it even if you tried (and the mca param doesn't show, so you'd *really* have to try).
This also involved a slight change to the oob.xcast API, so propagated that as required.
Note: this has *only* been tested on rsh, SLURM, and Bproc environments (now that it has been transferred to the OMPI trunk, I'll need to re-test it [only done rsh so far]). It should work fine on any environment that uses the ORTE daemons - anywhere else, you are on your own... :-)
Also, correct a mistake where the orte_debug_flag was declared an int, but the mca param was set as a bool. Move the storage for that flag to the orte/runtime/params.c and orte/runtime/params.h files appropriately.
This commit was SVN r14475.
2007-04-23 22:41:04 +04:00
|
|
|
}
|
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
CLEANUP:
|
2008-04-30 23:49:53 +04:00
|
|
|
|
2006-11-11 07:03:45 +03:00
|
|
|
return rc;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
static void set_handler_default(int sig)
|
|
|
|
{
|
|
|
|
struct sigaction act;
|
|
|
|
|
|
|
|
act.sa_handler = SIG_DFL;
|
|
|
|
act.sa_flags = 0;
|
|
|
|
sigemptyset(&act.sa_mask);
|
|
|
|
|
|
|
|
sigaction(sig, &act, (struct sigaction *)0);
|
|
|
|
}
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2009-05-22 18:59:27 +04:00
|
|
|
/**
|
|
|
|
* Send a sigal to a pid. Note that if we get an error, we set the
|
|
|
|
* return value and let the upper layer print out the message.
|
|
|
|
*/
|
2006-09-15 01:29:51 +04:00
|
|
|
static int send_signal(pid_t pid, int signal)
|
|
|
|
{
|
|
|
|
int rc = ORTE_SUCCESS;
|
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_odls_globals.output,
|
2007-09-12 18:32:31 +04:00
|
|
|
"%s sending signal %d to pid %ld",
|
2009-03-06 00:50:47 +03:00
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
2007-09-12 18:32:31 +04:00
|
|
|
signal, (long)pid));
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
if (kill(pid, signal) != 0) {
|
|
|
|
switch(errno) {
|
|
|
|
case EINVAL:
|
|
|
|
rc = ORTE_ERR_BAD_PARAM;
|
|
|
|
break;
|
|
|
|
case ESRCH:
|
2009-05-22 18:59:27 +04:00
|
|
|
/* This case can occur when we deliver a signal to a
|
|
|
|
process that is no longer there. This can happen if
|
|
|
|
we deliver a signal while the job is shutting down.
|
|
|
|
This does not indicate a real problem, so just
|
|
|
|
ignore the error. */
|
2006-09-15 01:29:51 +04:00
|
|
|
break;
|
|
|
|
case EPERM:
|
|
|
|
rc = ORTE_ERR_PERM;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
rc = ORTE_ERROR;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
2007-09-12 18:32:31 +04:00
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
static int orte_odls_default_signal_local_procs(const orte_process_name_t *proc, int32_t signal)
|
Bring in the code for routing xcast stage gate messages via the local orteds. This code is inactive unless you specifically request it via an mca param oob_xcast_mode (can be set to "linear" or "direct"). Direct mode is the old standard method where we send messages directly to each MPI process. Linear mode sends the xcast message via the orteds, with the HNP sending the message to each orted directly.
There is a binomial algorithm in the code (i.e., the HNP would send to a subset of the orteds, which then relay it on according to the typical log-2 algo), but that has a bug in it so the code won't let you select it even if you tried (and the mca param doesn't show, so you'd *really* have to try).
This also involved a slight change to the oob.xcast API, so propagated that as required.
Note: this has *only* been tested on rsh, SLURM, and Bproc environments (now that it has been transferred to the OMPI trunk, I'll need to re-test it [only done rsh so far]). It should work fine on any environment that uses the ORTE daemons - anywhere else, you are on your own... :-)
Also, correct a mistake where the orte_debug_flag was declared an int, but the mca param was set as a bool. Move the storage for that flag to the orte/runtime/params.c and orte/runtime/params.h files appropriately.
This commit was SVN r14475.
2007-04-23 22:41:04 +04:00
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
2007-10-10 19:02:10 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_odls_base_default_signal_local_procs(proc, signal, send_signal))) {
|
These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC.
The commit has been tested for C/R and Cray operations, and on Odin (SLURM, rsh) and RoadRunner (TM). I tried to update all environments, but obviously could not test them. I know that Windows needs some work, and have highlighted what is know to be needed in the odls process component.
This represents a lot of work by Brian, Tim P, Josh, and myself, with much advice from Jeff and others. For posterity, I have appended a copy of the email describing the work that was done:
As we have repeatedly noted, the modex operation in MPI_Init is the single greatest consumer of time during startup. To-date, we have executed that operation as an ORTE stage gate that held the process until a startup message containing all required modex (and OOB contact info - see #3 below) info could be sent to it. Each process would send its data to the HNP's registry, which assembled and sent the message when all processes had reported in.
In addition, ORTE had taken responsibility for monitoring process status as it progressed through a series of "stage gates". The process reported its status at each gate, and ORTE would then send a "release" message once all procs had reported in.
The incoming changes revamp these procedures in three ways:
1. eliminating the ORTE stage gate system and cleanly delineating responsibility between the OMPI and ORTE layers for MPI init/finalize. The modex stage gate (STG1) has been replaced by a collective operation in the modex itself that performs an allgather on the required modex info. The allgather is implemented using the orte_grpcomm framework since the BTL's are not active at that point. At the moment, the grpcomm framework only has a "basic" component analogous to OMPI's "basic" coll framework - I would recommend that the MPI team create additional, more advanced components to improve performance of this step.
The other stage gates have been replaced by orte_grpcomm barrier functions. We tried to use MPI barriers instead (since the BTL's are active at that point), but - as we discussed on the telecon - these are not currently true barriers so the job would hang when we fell through while messages were still in process. Note that the grpcomm barrier doesn't actually resolve that problem, but Brian has pointed out that we are unlikely to ever see it violated. Again, you might want to spend a little time on an advanced barrier algorithm as the one in "basic" is very simplistic.
Summarizing this change: ORTE no longer tracks process state nor has direct responsibility for synchronizing jobs. This is now done via collective operations within the MPI layer, albeit using ORTE collective communication services. I -strongly- urge the MPI team to implement advanced collective algorithms to improve the performance of this critical procedure.
2. reducing the volume of data exchanged during modex. Data in the modex consisted of the process name, the name of the node where that process is located (expressed as a string), plus a string representation of all contact info. The nodename was required in order for the modex to determine if the process was local or not - in addition, some people like to have it to print pretty error messages when a connection failed.
The size of this data has been reduced in three ways:
(a) reducing the size of the process name itself. The process name consisted of two 32-bit fields for the jobid and vpid. This is far larger than any current system, or system likely to exist in the near future, can support. Accordingly, the default size of these fields has been reduced to 16-bits, which means you can have 32k procs in each of 32k jobs. Since the daemons must have a vpid, and we require one daemon/node, this also restricts the default configuration to 32k nodes.
To support any future "mega-clusters", a configuration option --enable-jumbo-apps has been added. This option increases the jobid and vpid field sizes to 32-bits. Someday, if necessary, someone can add yet another option to increase them to 64-bits, I suppose.
(b) replacing the string nodename with an integer nodeid. Since we have one daemon/node, the nodeid corresponds to the local daemon's vpid. This replaces an often lengthy string with only 2 (or at most 4) bytes, a substantial reduction.
(c) when the mca param requesting that nodenames be sent to support pretty error messages, a second mca param is now used to request FQDN - otherwise, the domain name is stripped (by default) from the message to save space. If someone wants to combine those into a single param somehow (perhaps with an argument?), they are welcome to do so - I didn't want to alter what people are already using.
While these may seem like small savings, they actually amount to a significant impact when aggregated across the entire modex operation. Since every proc must receive the modex data regardless of the collective used to send it, just reducing the size of the process name removes nearly 400MBytes of communication from a 32k proc job (admittedly, much of this comm may occur in parallel). So it does add up pretty quickly.
3. routing RML messages to reduce connections. The default messaging system remains point-to-point - i.e., each proc opens a socket to every proc it communicates with and sends its messages directly. A new option uses the orteds as routers - i.e., each proc only opens a single socket to its local orted. All messages are sent from the proc to the orted, which forwards the message to the orted on the node where the intended recipient proc is located - that orted then forwards the message to its local proc (the recipient). This greatly reduces the connection storm we have encountered during startup.
It also has the benefit of removing the sharing of every proc's OOB contact with every other proc. The orted routing tables are populated during launch since every orted gets a map of where every proc is being placed. Each proc, therefore, only needs to know the contact info for its local daemon, which is passed in via the environment when the proc is fork/exec'd by the daemon. This alone removes ~50 bytes/process of communication that was in the current STG1 startup message - so for our 32k proc job, this saves us roughly 32k*50 = 1.6MBytes sent to 32k procs = 51GBytes of messaging.
Note that you can use the new routing method by specifying -mca routed tree - if you so desire. This mode will become the default at some point in the future.
There are a few minor additional changes in the commit that I'll just note in passing:
* propagation of command line mca params to the orteds - fixes ticket #1073. See note there for details.
* requiring of "finalize" prior to "exit" for MPI procs - fixes ticket #1144. See note there for details.
* cleanup of some stale header files
This commit was SVN r16364.
2007-10-05 23:48:23 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
}
|