2007-07-20 05:34:02 +04:00
|
|
|
/*
|
|
|
|
|
* $COPYRIGHT$
|
|
|
|
|
*
|
|
|
|
|
* Additional copyrights may follow
|
|
|
|
|
*
|
|
|
|
|
* $HEADER$
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include "orte_config.h"
|
|
|
|
|
|
|
|
|
|
#include "opal/mca/mca.h"
|
2007-07-20 07:24:52 +04:00
|
|
|
#include "opal/util/output.h"
|
2007-07-20 05:34:02 +04:00
|
|
|
#include "opal/mca/base/mca_base_component_repository.h"
|
|
|
|
|
#include "orte/mca/rml/rml.h"
|
|
|
|
|
#include "orte/mca/rml/base/base.h"
|
|
|
|
|
#include "orte/dss/dss.h"
|
|
|
|
|
#include "orte/dss/dss_types.h"
|
|
|
|
|
#include "orte/mca/errmgr/errmgr.h"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* The following file was created by configure. It contains extern
|
|
|
|
|
* statements and the definition of an array of pointers to each
|
|
|
|
|
* component's public mca_base_component_t struct. */
|
|
|
|
|
#include "orte/mca/rml/base/static-components.h"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
int orte_rml_base_output = -1;
|
|
|
|
|
opal_list_t orte_rml_base_subscriptions;
|
|
|
|
|
orte_rml_module_t orte_rml;
|
|
|
|
|
opal_list_t orte_rml_base_components;
|
|
|
|
|
orte_rml_component_t *orte_rml_component = NULL;
|
|
|
|
|
|
|
|
|
|
static bool component_open_called = false;
|
|
|
|
|
|
|
|
|
|
int
|
|
|
|
|
orte_rml_base_open(void)
|
|
|
|
|
{
|
|
|
|
|
int ret;
|
|
|
|
|
orte_data_type_t tmp;
|
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
|
|
|
int param, value;
|
2007-07-20 05:34:02 +04:00
|
|
|
|
|
|
|
|
/* Initialize globals */
|
|
|
|
|
OBJ_CONSTRUCT(&orte_rml_base_components, opal_list_t);
|
|
|
|
|
OBJ_CONSTRUCT(&orte_rml_base_subscriptions, opal_list_t);
|
|
|
|
|
|
|
|
|
|
/* register the base system types with the DPS */
|
|
|
|
|
tmp = ORTE_RML_TAG;
|
|
|
|
|
if (ORTE_SUCCESS != (ret = orte_dss.register_type(orte_rml_base_pack_tag,
|
|
|
|
|
orte_rml_base_unpack_tag,
|
|
|
|
|
(orte_dss_copy_fn_t)orte_rml_base_copy_tag,
|
|
|
|
|
(orte_dss_compare_fn_t)orte_rml_base_compare_tags,
|
|
|
|
|
(orte_dss_size_fn_t)orte_rml_base_size_tag,
|
|
|
|
|
(orte_dss_print_fn_t)orte_rml_base_print_tag,
|
|
|
|
|
(orte_dss_release_fn_t)orte_rml_base_std_obj_release,
|
|
|
|
|
ORTE_DSS_UNSTRUCTURED,
|
|
|
|
|
"ORTE_RML_TAG", &tmp))) {
|
|
|
|
|
ORTE_ERROR_LOG(ret);
|
|
|
|
|
return ret;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Which RML Wrapper component to use, if any
|
|
|
|
|
* - NULL or "" = No wrapper
|
|
|
|
|
* - ow. select that specific wrapper component
|
|
|
|
|
*/
|
|
|
|
|
mca_base_param_reg_string_name("rml", "wrapper",
|
|
|
|
|
"Use a Wrapper component around the selected RML component",
|
|
|
|
|
false, false,
|
|
|
|
|
NULL, NULL);
|
|
|
|
|
|
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
|
|
|
/* register parameters */
|
|
|
|
|
param = mca_base_param_reg_int_name("rml", "base_verbose",
|
|
|
|
|
"Verbosity level for the rml framework",
|
|
|
|
|
false, false, 0, &value);
|
|
|
|
|
if (value != 0) {
|
|
|
|
|
orte_rml_base_output = opal_output_open(NULL);
|
|
|
|
|
} else {
|
|
|
|
|
orte_rml_base_output = -1;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2007-07-20 05:34:02 +04:00
|
|
|
/* Open up all available components */
|
|
|
|
|
ret = mca_base_components_open("rml",
|
|
|
|
|
orte_rml_base_output,
|
|
|
|
|
mca_rml_base_static_components,
|
|
|
|
|
&orte_rml_base_components,
|
|
|
|
|
true);
|
|
|
|
|
component_open_called = true;
|
|
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
int
|
|
|
|
|
orte_rml_base_select(void)
|
|
|
|
|
{
|
|
|
|
|
opal_list_item_t *item;
|
|
|
|
|
|
|
|
|
|
int selected_priority = -1;
|
|
|
|
|
orte_rml_component_t *selected_component = NULL;
|
|
|
|
|
orte_rml_module_t *selected_module = NULL;
|
|
|
|
|
|
|
|
|
|
int wrapper_priority = -1;
|
|
|
|
|
orte_rml_component_t *wrapper_component = NULL;
|
|
|
|
|
orte_rml_module_t *wrapper_module = NULL;
|
|
|
|
|
char *rml_wrapper = NULL;
|
|
|
|
|
|
|
|
|
|
mca_base_param_reg_string_name("rml", "wrapper",
|
|
|
|
|
"Use a Wrapper component around the selected RML component",
|
|
|
|
|
false, false,
|
|
|
|
|
NULL, &rml_wrapper);
|
|
|
|
|
|
|
|
|
|
for (item = opal_list_get_first(&orte_rml_base_components);
|
|
|
|
|
item != opal_list_get_end(&orte_rml_base_components) ;
|
|
|
|
|
item = opal_list_get_next(item)) {
|
|
|
|
|
mca_base_component_list_item_t *cli;
|
|
|
|
|
orte_rml_component_t* component;
|
|
|
|
|
|
|
|
|
|
cli = (mca_base_component_list_item_t *) item;
|
|
|
|
|
component = (orte_rml_component_t *) cli->cli_component;
|
|
|
|
|
|
|
|
|
|
opal_output_verbose(10, orte_rml_base_output,
|
|
|
|
|
"orte_rml_base_select: initializing %s component %s",
|
|
|
|
|
component->rml_version.mca_type_name,
|
|
|
|
|
component->rml_version.mca_component_name);
|
|
|
|
|
|
|
|
|
|
if (NULL == component->rml_init) {
|
|
|
|
|
opal_output_verbose(10, orte_rml_base_output,
|
|
|
|
|
"orte_rml_base_select: no init function; ignoring component");
|
|
|
|
|
} else {
|
|
|
|
|
int priority = 0;
|
|
|
|
|
|
|
|
|
|
orte_rml_module_t* module = component->rml_init(&priority);
|
|
|
|
|
if (NULL == module) {
|
|
|
|
|
opal_output_verbose(10, orte_rml_base_output,
|
|
|
|
|
"orte_rml_base_select: init returned failure");
|
|
|
|
|
continue;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if(NULL != rml_wrapper &&
|
|
|
|
|
/* If this is a wrapper component then save it for later */
|
|
|
|
|
RML_SELECT_WRAPPER_PRIORITY >= priority) {
|
|
|
|
|
if( 0 == strncmp(component->rml_version.mca_component_name,
|
|
|
|
|
rml_wrapper,
|
|
|
|
|
strlen(rml_wrapper) ) ) {
|
|
|
|
|
wrapper_priority = priority;
|
|
|
|
|
wrapper_component = component;
|
|
|
|
|
wrapper_module = module;
|
|
|
|
|
}
|
|
|
|
|
} else if (priority > selected_priority) {
|
|
|
|
|
/* Otherwise this is a normal module and subject to normal selection */
|
|
|
|
|
if (NULL != selected_module && NULL != selected_module->finalize) {
|
|
|
|
|
selected_module->finalize();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
selected_priority = priority;
|
|
|
|
|
selected_component = component;
|
|
|
|
|
selected_module = module;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Unload all components that were not selected
|
|
|
|
|
*/
|
|
|
|
|
item = opal_list_get_first(&orte_rml_base_components);
|
|
|
|
|
while (item != opal_list_get_end(&orte_rml_base_components)) {
|
|
|
|
|
opal_list_item_t* next = opal_list_get_next(item);
|
|
|
|
|
orte_rml_component_t* component;
|
|
|
|
|
mca_base_component_list_item_t *cli;
|
|
|
|
|
|
|
|
|
|
cli = (mca_base_component_list_item_t *) item;
|
|
|
|
|
component = (orte_rml_component_t *) cli->cli_component;
|
|
|
|
|
|
|
|
|
|
/* Keep it if it is the wrapper component */
|
|
|
|
|
if (NULL != wrapper_component &&
|
|
|
|
|
component == wrapper_component) {
|
|
|
|
|
item = next;
|
|
|
|
|
continue;
|
|
|
|
|
}
|
|
|
|
|
/* Not the selected component */
|
|
|
|
|
if (component != selected_component) {
|
|
|
|
|
opal_output_verbose(10, orte_rml_base_output,
|
|
|
|
|
"orte_rml_base_select: module %s unloaded",
|
|
|
|
|
component->rml_version.mca_component_name);
|
|
|
|
|
|
|
|
|
|
mca_base_component_repository_release((mca_base_component_t *) component);
|
|
|
|
|
opal_list_remove_item(&orte_rml_base_components, item);
|
|
|
|
|
OBJ_RELEASE(item);
|
|
|
|
|
}
|
|
|
|
|
item = next;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* setup reference to selected module */
|
|
|
|
|
if (NULL != selected_module) {
|
|
|
|
|
orte_rml = *selected_module;
|
|
|
|
|
orte_rml_component = selected_component;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* If a wrapper component was requested then
|
|
|
|
|
* Make sure it can switch out the selected module
|
|
|
|
|
*/
|
|
|
|
|
if( NULL != wrapper_component) {
|
|
|
|
|
wrapper_component->rml_init(NULL);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if( NULL != rml_wrapper ) {
|
|
|
|
|
free(rml_wrapper);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (NULL == selected_component) return ORTE_ERROR;
|
|
|
|
|
|
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
int
|
|
|
|
|
orte_rml_base_close(void)
|
|
|
|
|
{
|
|
|
|
|
/* shutdown any remaining opened components */
|
|
|
|
|
if (component_open_called) {
|
|
|
|
|
mca_base_components_close(orte_rml_base_output,
|
|
|
|
|
&orte_rml_base_components, NULL);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
OBJ_DESTRUCT(&orte_rml_base_components);
|
|
|
|
|
OBJ_DESTRUCT(&orte_rml_base_subscriptions);
|
|
|
|
|
|
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
|
}
|