2005-03-14 23:57:21 +03:00
/*
2008-05-06 22:08:45 +04:00
* Copyright ( c ) 2004 - 2008 The Trustees of Indiana University and Indiana
2005-11-05 22:57:48 +03:00
* University Research and Technology
* Corporation . All rights reserved .
* Copyright ( c ) 2004 - 2005 The University of Tennessee and The University
* of Tennessee Research Foundation . All rights
* reserved .
2005-03-14 23:57:21 +03:00
* Copyright ( c ) 2004 - 2005 High Performance Computing Center Stuttgart ,
* University of Stuttgart . All rights reserved .
2005-03-24 15:43:37 +03:00
* Copyright ( c ) 2004 - 2005 The Regents of the University of California .
* All rights reserved .
2006-07-05 00:12:35 +04:00
* Copyright ( c ) 2006 Cisco Systems , Inc . All rights reserved .
2005-03-14 23:57:21 +03:00
* $ COPYRIGHT $
*
* Additional copyrights may follow
*
* $ HEADER $
*
* These symbols are in a file by themselves to provide nice linker
* semantics . Since linkers generally pull in symbols by object
* files , keeping these symbols as the only symbols in this file
* prevents utility programs such as " ompi_info " from having to import
* entire components just to query their version and parameters .
*/
2006-02-12 04:33:29 +03:00
# include "orte_config.h"
2008-02-28 04:57:57 +03:00
# include "orte/constants.h"
2005-03-14 23:57:21 +03:00
2005-08-25 02:20:51 +04:00
# include "opal/mca/base/mca_base_param.h"
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
# include "orte/util/output.h"
2005-10-04 23:38:51 +04:00
# include "opal/util/argv.h"
2006-09-15 01:29:51 +04:00
# include "orte/util/proc_info.h"
# include "orte/mca/errmgr/errmgr.h"
2008-02-28 04:57:57 +03:00
# include "orte/mca/plm/plm.h"
# include "orte/mca/plm/base/base.h"
# include "orte/mca/plm/base/plm_private.h"
# include "plm_tm.h"
2005-03-14 23:57:21 +03:00
/*
2008-02-28 04:57:57 +03:00
* Public string showing the plm ompi_tm component version number
2005-03-14 23:57:21 +03:00
*/
2008-02-28 04:57:57 +03:00
const char * mca_plm_tm_component_version_string =
" Open MPI tm plm MCA component version " ORTE_VERSION ;
2005-03-14 23:57:21 +03:00
/*
* Local function
*/
2008-02-28 04:57:57 +03:00
static int plm_tm_open ( void ) ;
static int plm_tm_close ( void ) ;
2008-05-06 22:08:45 +04:00
static int orte_plm_tm_component_query ( mca_base_module_t * * module , int * priority ) ;
2005-03-14 23:57:21 +03:00
/*
* Instantiate the public struct with all of our public information
* and pointers to our public functions in it
*/
2008-02-28 04:57:57 +03:00
orte_plm_tm_component_t mca_plm_tm_component = {
2005-03-14 23:57:21 +03:00
{
2005-08-19 20:49:59 +04:00
/* First, the mca_component_t struct containing meta information
about the component itself */
{
2008-02-28 04:57:57 +03:00
/* Indicate that we are a plm v1.0.0 component (which also
2005-08-19 20:49:59 +04:00
implies a specific MCA version ) */
2008-02-28 04:57:57 +03:00
ORTE_PLM_BASE_VERSION_1_0_0 ,
2005-08-19 20:49:59 +04:00
/* Component name and version */
" tm " ,
ORTE_MAJOR_VERSION ,
ORTE_MINOR_VERSION ,
ORTE_RELEASE_VERSION ,
/* Component open and close functions */
2008-02-28 04:57:57 +03:00
plm_tm_open ,
plm_tm_close ,
2008-05-06 22:08:45 +04:00
orte_plm_tm_component_query
2005-08-19 20:49:59 +04:00
} ,
/* Next the MCA v1.0.0 component meta data */
{
2007-03-17 02:11:45 +03:00
/* The component is checkpoint ready */
MCA_BASE_METADATA_PARAM_CHECKPOINT
2008-05-06 22:08:45 +04:00
}
2005-08-19 20:49:59 +04:00
}
2005-03-14 23:57:21 +03:00
} ;
2008-02-28 04:57:57 +03:00
static int plm_tm_open ( void )
2005-03-14 23:57:21 +03:00
{
2008-02-28 04:57:57 +03:00
int tmp ;
2008-05-06 22:08:45 +04:00
mca_base_component_t * comp = & mca_plm_tm_component . super . base_version ;
2005-08-19 20:49:59 +04:00
2005-10-04 23:38:51 +04:00
mca_base_param_reg_string ( comp , " orted " ,
" Command to use to start proxy orted " ,
false , false , " orted " ,
2008-02-28 04:57:57 +03:00
& mca_plm_tm_component . orted ) ;
2005-10-04 23:38:51 +04:00
mca_base_param_reg_int ( comp , " want_path_check " ,
2008-02-28 04:57:57 +03:00
" Whether the launching process should check for the plm_tm_orted executable in the PATH before launching (the TM API does not give an idication of failure; this is a somewhat-lame workaround; non-zero values enable this check) " ,
2005-10-04 23:38:51 +04:00
false , false , ( int ) true , & tmp ) ;
2008-02-28 04:57:57 +03:00
mca_plm_tm_component . want_path_check = OPAL_INT_TO_BOOL ( tmp ) ;
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
2008-02-28 04:57:57 +03:00
mca_plm_tm_component . checked_paths = NULL ;
2008-06-03 01:46:34 +04:00
2005-10-04 23:38:51 +04:00
return ORTE_SUCCESS ;
}
2008-02-28 04:57:57 +03:00
static int plm_tm_close ( void )
2005-10-04 23:38:51 +04:00
{
2008-02-28 04:57:57 +03:00
if ( NULL ! = mca_plm_tm_component . checked_paths ) {
opal_argv_free ( mca_plm_tm_component . checked_paths ) ;
2005-10-04 23:38:51 +04:00
}
2005-03-14 23:57:21 +03:00
return ORTE_SUCCESS ;
}
2008-05-06 22:08:45 +04:00
static int orte_plm_tm_component_query ( mca_base_module_t * * module , int * priority )
2005-03-14 23:57:21 +03:00
{
/* Are we running under a TM job? */
if ( NULL ! = getenv ( " PBS_ENVIRONMENT " ) & &
NULL ! = getenv ( " PBS_JOBID " ) ) {
2006-09-15 01:29:51 +04:00
2008-02-28 04:57:57 +03:00
* priority = 75 ;
2008-05-06 22:08:45 +04:00
* module = ( mca_base_module_t * ) & orte_plm_tm_module ;
return ORTE_SUCCESS ;
2005-03-14 23:57:21 +03:00
}
/* Sadly, no */
2008-05-06 22:08:45 +04:00
* module = NULL ;
2008-05-07 01:26:17 +04:00
return ORTE_ERROR ;
2005-03-14 23:57:21 +03:00
}