2012-06-28 22:23:34 +04:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2004-2010 The Trustees of Indiana University and Indiana
|
|
|
|
* University Research and Technology
|
|
|
|
* Corporation. All rights reserved.
|
|
|
|
* Copyright (c) 2004-2011 The University of Tennessee and The University
|
|
|
|
* of Tennessee Research Foundation. All rights
|
|
|
|
* reserved.
|
|
|
|
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
|
|
* University of Stuttgart. All rights reserved.
|
|
|
|
* Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
* All rights reserved.
|
|
|
|
* Copyright (c) 2006-2012 Cisco Systems, Inc. All rights reserved.
|
Per the meeting on moving the BTLs to OPAL, move the ORTE database "db" framework to OPAL so the relocated BTLs can access it. Because the data is indexed by process, this requires that we define a new "opal_identifier_t" that corresponds to the orte_process_name_t struct. In order to support multiple run-times, this is defined in opal/mca/db/db_types.h as a uint64_t without identifying the meaning of any part of that data.
A few changes were required to support this move:
1. the PMI component used to identify rte-related data (e.g., host name, bind level) and package them as a unit to reduce the number of PMI keys. This code was moved up to the ORTE layer as the OPAL layer has no understanding of these concepts. In addition, the component locally stored data based on process jobid/vpid - this could no longer be supported (see below for the solution).
2. the hash component was updated to use the new opal_identifier_t instead of orte_process_name_t as its index for storing data in the hash tables. Previously, we did a hash on the vpid and stored the data in a 32-bit hash table. In the revised system, we don't see a separate "vpid" field - we only have a 64-bit opaque value. The orte_process_name_t hash turned out to do nothing useful, so we now store the data in a 64-bit hash table. Preliminary tests didn't show any identifiable change in behavior or performance, but we'll have to see if a move back to the 32-bit table is required at some later time.
3. the db framework was a "select one" system. However, since the PMI component could no longer use its internal storage system, the framework has now been changed to a "select many" mode of operation. This allows the hash component to handle all internal storage, while the PMI component only handles pushing/pulling things from the PMI system. This was something we had planned for some time - when fetching data, we first check internal storage to see if we already have it, and then automatically go to the global system to look for it if we don't. Accordingly, the framework was provided with a custom query function used during "select" that lets you seperately specify the "store" and "fetch" ordering.
4. the ORTE grpcomm and ess/pmi components, and the nidmap code, were updated to work with the new db framework and to specify internal/global storage options.
No changes were made to the MPI layer, except for modifying the ORTE component of the OMPI/rte framework to support the new db framework.
This commit was SVN r28112.
2013-02-26 21:50:04 +04:00
|
|
|
* Copyright (c) 2010-2013 Los Alamos National Security, LLC.
|
2012-06-28 22:23:34 +04:00
|
|
|
* All rights reserved.
|
|
|
|
* Copyright (c) 2011-2012 University of Houston. All rights reserved.
|
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "orte_config.h"
|
|
|
|
#include "orte/constants.h"
|
|
|
|
#include "orte/types.h"
|
|
|
|
|
|
|
|
#include "opal/class/opal_pointer_array.h"
|
2013-03-28 01:17:31 +04:00
|
|
|
#include "opal/util/argv.h"
|
2012-06-28 22:23:34 +04:00
|
|
|
#include "opal/runtime/opal_info_support.h"
|
|
|
|
|
2013-03-28 01:17:31 +04:00
|
|
|
#include "orte/include/orte/frameworks.h"
|
2012-06-28 22:23:34 +04:00
|
|
|
#include "orte/util/proc_info.h"
|
|
|
|
#include "orte/runtime/runtime.h"
|
2013-03-28 01:17:31 +04:00
|
|
|
#include "orte/runtime/orte_globals.h"
|
2012-06-28 22:23:34 +04:00
|
|
|
|
|
|
|
#include "orte/runtime/orte_info_support.h"
|
|
|
|
|
|
|
|
const char *orte_info_type_orte = "orte";
|
|
|
|
|
|
|
|
void orte_info_register_types(opal_pointer_array_t *mca_types)
|
|
|
|
{
|
2013-03-28 01:17:31 +04:00
|
|
|
int i;
|
|
|
|
|
|
|
|
/* add the top-level type */
|
2012-06-28 22:23:34 +04:00
|
|
|
opal_pointer_array_add(mca_types, "orte");
|
2013-03-28 01:17:31 +04:00
|
|
|
|
|
|
|
/* push all the types found by autogen */
|
|
|
|
for (i=0; NULL != orte_frameworks[i]; i++) {
|
|
|
|
opal_pointer_array_add(mca_types, orte_frameworks[i]->framework_name);
|
|
|
|
}
|
2012-06-28 22:23:34 +04:00
|
|
|
}
|
|
|
|
|
2013-03-28 01:14:43 +04:00
|
|
|
static int info_register_framework (mca_base_framework_t *framework, opal_pointer_array_t *component_map) {
|
|
|
|
opal_info_component_map_t *map;
|
|
|
|
int rc;
|
|
|
|
|
2013-03-28 01:17:31 +04:00
|
|
|
rc = mca_base_framework_register(framework, MCA_BASE_REGISTER_ALL);
|
|
|
|
if (OPAL_SUCCESS != rc && OPAL_ERR_BAD_PARAM != rc) {
|
2013-03-28 01:14:43 +04:00
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
map = OBJ_NEW(opal_info_component_map_t);
|
|
|
|
map->type = strdup(framework->framework_name);
|
|
|
|
map->components = &framework->framework_components;
|
|
|
|
opal_pointer_array_add(component_map, map);
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
2013-03-28 01:17:31 +04:00
|
|
|
int orte_info_register_framework_params(opal_pointer_array_t *component_map)
|
2012-06-28 22:23:34 +04:00
|
|
|
{
|
2013-03-28 01:56:46 +04:00
|
|
|
char *str=NULL;
|
Refs trac:3275.
We ran into a case where the OMPI SVN trunk grew a new acceptable MCA
parameter value, but this new value was not accepted on the v1.6
branch (hwloc_base_mem_bind_failure_action -- on the trunk it accepts
the value "silent", but on the older v1.6 branch, it doesn't). If you
set "hwloc_base_mem_bind_failure_action=silent" in the default MCA
params file and then accidentally ran with the v1.6 branch, every OMPI
executable (including ompi_info) just failed because hwloc_base_open()
would say "hey, 'silent' is not a valid value for
hwloc_base_mem_bind_failure_action!". Kaboom.
The only problem is that it didn't give you any indication of where
this value was being set. Quite maddening, from a user perspective.
So we changed the ompi_info handles this case. If any framework open
function return OMPI_ERR_BAD_PARAM (either because its base MCA params
got a bad value or because one of its component register/open
functions return OMPI_ERR_BAD_PARAM), ompi_info will stop, print out
a warning that it received and error, and then dump out the parameters
that it has received so far in the framework that had a problem.
At a minimum, this will show the user the MCA param that had an error
(it's usually the last one), and ''where it was set from'' (so that
they can go fix it).
We updated ompi_info to check for O???_ERR_BAD_PARAM from each from
the framework opens. Also updated the doxygen docs in mca.h for this
O???_BAD_PARAM behavior. And we noticed that mca.h had MCA_SUCCESS
and MCA_ERR_??? codes. Why? I think we used them in exactly one
place in the code base (mca_base_components_open.c). So we deleted
those and just used the normal OPAL_* codes instead.
While we were doing this, we also cleaned up a little memory
management during ompi_info/orte-info/opal-info finalization.
Valgrind still reports a truckload of memory still in use at ompi_info
termination, but they mostly look to be components not freeing
memory/resources properly (and outside the scope of this fix).
This commit was SVN r27306.
The following Trac tickets were found above:
Ticket 3275 --> https://svn.open-mpi.org/trac/ompi/ticket/3275
2012-09-12 00:47:24 +04:00
|
|
|
int i, rc;
|
2012-06-28 22:23:34 +04:00
|
|
|
|
|
|
|
/* Register the ORTE layer's MCA parameters */
|
|
|
|
|
Refs trac:3275.
We ran into a case where the OMPI SVN trunk grew a new acceptable MCA
parameter value, but this new value was not accepted on the v1.6
branch (hwloc_base_mem_bind_failure_action -- on the trunk it accepts
the value "silent", but on the older v1.6 branch, it doesn't). If you
set "hwloc_base_mem_bind_failure_action=silent" in the default MCA
params file and then accidentally ran with the v1.6 branch, every OMPI
executable (including ompi_info) just failed because hwloc_base_open()
would say "hey, 'silent' is not a valid value for
hwloc_base_mem_bind_failure_action!". Kaboom.
The only problem is that it didn't give you any indication of where
this value was being set. Quite maddening, from a user perspective.
So we changed the ompi_info handles this case. If any framework open
function return OMPI_ERR_BAD_PARAM (either because its base MCA params
got a bad value or because one of its component register/open
functions return OMPI_ERR_BAD_PARAM), ompi_info will stop, print out
a warning that it received and error, and then dump out the parameters
that it has received so far in the framework that had a problem.
At a minimum, this will show the user the MCA param that had an error
(it's usually the last one), and ''where it was set from'' (so that
they can go fix it).
We updated ompi_info to check for O???_ERR_BAD_PARAM from each from
the framework opens. Also updated the doxygen docs in mca.h for this
O???_BAD_PARAM behavior. And we noticed that mca.h had MCA_SUCCESS
and MCA_ERR_??? codes. Why? I think we used them in exactly one
place in the code base (mca_base_components_open.c). So we deleted
those and just used the normal OPAL_* codes instead.
While we were doing this, we also cleaned up a little memory
management during ompi_info/orte-info/opal-info finalization.
Valgrind still reports a truckload of memory still in use at ompi_info
termination, but they mostly look to be components not freeing
memory/resources properly (and outside the scope of this fix).
This commit was SVN r27306.
The following Trac tickets were found above:
Ticket 3275 --> https://svn.open-mpi.org/trac/ompi/ticket/3275
2012-09-12 00:47:24 +04:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_register_params()) &&
|
|
|
|
ORTE_ERR_BAD_PARAM != rc) {
|
|
|
|
str = "orte_register_params";
|
|
|
|
goto error;
|
2012-06-28 22:23:34 +04:00
|
|
|
}
|
|
|
|
|
2013-03-28 01:17:31 +04:00
|
|
|
for (i=0; NULL != orte_frameworks[i]; i++) {
|
|
|
|
if (OPAL_SUCCESS != (rc = info_register_framework(orte_frameworks[i], component_map))) {
|
|
|
|
fprintf (stderr, "rc = %d\n", rc);
|
|
|
|
str = orte_frameworks[i]->framework_name;
|
|
|
|
goto error;
|
2012-06-28 22:23:34 +04:00
|
|
|
}
|
|
|
|
}
|
Refs trac:3275.
We ran into a case where the OMPI SVN trunk grew a new acceptable MCA
parameter value, but this new value was not accepted on the v1.6
branch (hwloc_base_mem_bind_failure_action -- on the trunk it accepts
the value "silent", but on the older v1.6 branch, it doesn't). If you
set "hwloc_base_mem_bind_failure_action=silent" in the default MCA
params file and then accidentally ran with the v1.6 branch, every OMPI
executable (including ompi_info) just failed because hwloc_base_open()
would say "hey, 'silent' is not a valid value for
hwloc_base_mem_bind_failure_action!". Kaboom.
The only problem is that it didn't give you any indication of where
this value was being set. Quite maddening, from a user perspective.
So we changed the ompi_info handles this case. If any framework open
function return OMPI_ERR_BAD_PARAM (either because its base MCA params
got a bad value or because one of its component register/open
functions return OMPI_ERR_BAD_PARAM), ompi_info will stop, print out
a warning that it received and error, and then dump out the parameters
that it has received so far in the framework that had a problem.
At a minimum, this will show the user the MCA param that had an error
(it's usually the last one), and ''where it was set from'' (so that
they can go fix it).
We updated ompi_info to check for O???_ERR_BAD_PARAM from each from
the framework opens. Also updated the doxygen docs in mca.h for this
O???_BAD_PARAM behavior. And we noticed that mca.h had MCA_SUCCESS
and MCA_ERR_??? codes. Why? I think we used them in exactly one
place in the code base (mca_base_components_open.c). So we deleted
those and just used the normal OPAL_* codes instead.
While we were doing this, we also cleaned up a little memory
management during ompi_info/orte-info/opal-info finalization.
Valgrind still reports a truckload of memory still in use at ompi_info
termination, but they mostly look to be components not freeing
memory/resources properly (and outside the scope of this fix).
This commit was SVN r27306.
The following Trac tickets were found above:
Ticket 3275 --> https://svn.open-mpi.org/trac/ompi/ticket/3275
2012-09-12 00:47:24 +04:00
|
|
|
|
|
|
|
if (ORTE_ERR_BAD_PARAM == rc) {
|
2013-03-28 01:56:46 +04:00
|
|
|
fprintf(stderr, "\nA \"bad parameter\" error was encountered when opening the ORTE %s framework\n",
|
|
|
|
(NULL == str) ? "NULL" : str);
|
Refs trac:3275.
We ran into a case where the OMPI SVN trunk grew a new acceptable MCA
parameter value, but this new value was not accepted on the v1.6
branch (hwloc_base_mem_bind_failure_action -- on the trunk it accepts
the value "silent", but on the older v1.6 branch, it doesn't). If you
set "hwloc_base_mem_bind_failure_action=silent" in the default MCA
params file and then accidentally ran with the v1.6 branch, every OMPI
executable (including ompi_info) just failed because hwloc_base_open()
would say "hey, 'silent' is not a valid value for
hwloc_base_mem_bind_failure_action!". Kaboom.
The only problem is that it didn't give you any indication of where
this value was being set. Quite maddening, from a user perspective.
So we changed the ompi_info handles this case. If any framework open
function return OMPI_ERR_BAD_PARAM (either because its base MCA params
got a bad value or because one of its component register/open
functions return OMPI_ERR_BAD_PARAM), ompi_info will stop, print out
a warning that it received and error, and then dump out the parameters
that it has received so far in the framework that had a problem.
At a minimum, this will show the user the MCA param that had an error
(it's usually the last one), and ''where it was set from'' (so that
they can go fix it).
We updated ompi_info to check for O???_ERR_BAD_PARAM from each from
the framework opens. Also updated the doxygen docs in mca.h for this
O???_BAD_PARAM behavior. And we noticed that mca.h had MCA_SUCCESS
and MCA_ERR_??? codes. Why? I think we used them in exactly one
place in the code base (mca_base_components_open.c). So we deleted
those and just used the normal OPAL_* codes instead.
While we were doing this, we also cleaned up a little memory
management during ompi_info/orte-info/opal-info finalization.
Valgrind still reports a truckload of memory still in use at ompi_info
termination, but they mostly look to be components not freeing
memory/resources properly (and outside the scope of this fix).
This commit was SVN r27306.
The following Trac tickets were found above:
Ticket 3275 --> https://svn.open-mpi.org/trac/ompi/ticket/3275
2012-09-12 00:47:24 +04:00
|
|
|
fprintf(stderr, "The output received from that framework includes the following parameters:\n\n");
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
error:
|
|
|
|
fprintf(stderr, "orte_info_register: %s failed\n", str);
|
|
|
|
return ORTE_ERROR;
|
2012-06-28 22:23:34 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
void orte_info_close_components(void)
|
|
|
|
{
|
2013-03-28 01:17:31 +04:00
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i=0; NULL != orte_frameworks[i]; i++) {
|
|
|
|
(void) mca_base_framework_close(orte_frameworks[i]);
|
|
|
|
}
|
2012-06-28 22:23:34 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
void orte_info_show_orte_version(const char *scope)
|
|
|
|
{
|
|
|
|
char *tmp, *tmp2;
|
|
|
|
|
|
|
|
asprintf(&tmp, "%s:version:full", orte_info_type_orte);
|
|
|
|
tmp2 = opal_info_make_version_str(scope,
|
|
|
|
ORTE_MAJOR_VERSION, ORTE_MINOR_VERSION,
|
|
|
|
ORTE_RELEASE_VERSION,
|
|
|
|
ORTE_GREEK_VERSION,
|
|
|
|
ORTE_WANT_REPO_REV, ORTE_REPO_REV);
|
|
|
|
opal_info_out("Open RTE", tmp, tmp2);
|
|
|
|
free(tmp);
|
|
|
|
free(tmp2);
|
|
|
|
asprintf(&tmp, "%s:version:repo", orte_info_type_orte);
|
|
|
|
opal_info_out("Open RTE repo revision", tmp, ORTE_REPO_REV);
|
|
|
|
free(tmp);
|
|
|
|
asprintf(&tmp, "%s:version:release_date", orte_info_type_orte);
|
|
|
|
opal_info_out("Open RTE release date", tmp, ORTE_RELEASE_DATE);
|
|
|
|
free(tmp);
|
|
|
|
}
|
|
|
|
|