2005-11-07 01:05:50 +03:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
|
|
* University Research and Technology
|
|
|
|
* Corporation. All rights reserved.
|
2006-04-20 03:42:06 +04:00
|
|
|
* Copyright (c) 2004-2006 The University of Tennessee and The University
|
2005-11-07 01:05:50 +03: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.
|
2008-05-07 06:31:24 +04:00
|
|
|
* Copyright (c) 2008 Sun Microsystems, Inc. All rights reserved.
|
2005-11-07 01:05:50 +03:00
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "ompi_config.h"
|
|
|
|
|
|
|
|
#include "mpi.h"
|
2006-02-12 04:33:29 +03:00
|
|
|
#include "ompi/constants.h"
|
|
|
|
#include "ompi/datatype/datatype.h"
|
|
|
|
#include "ompi/communicator/communicator.h"
|
|
|
|
#include "opal/mca/base/mca_base_param.h"
|
|
|
|
#include "ompi/mca/coll/base/base.h"
|
|
|
|
#include "ompi/mca/coll/coll.h"
|
|
|
|
#include "ompi/mca/coll/base/coll_tags.h"
|
2005-11-07 01:05:50 +03:00
|
|
|
#include "coll_tuned.h"
|
2006-02-12 04:33:29 +03:00
|
|
|
#include "ompi/mca/pml/pml.h"
|
2005-11-07 01:05:50 +03:00
|
|
|
#include "opal/util/bit_ops.h"
|
|
|
|
|
|
|
|
#include "coll_tuned.h"
|
|
|
|
|
2005-11-11 07:49:29 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Notes on evaluation rules and ordering
|
|
|
|
*
|
|
|
|
* The order is:
|
|
|
|
* use file based rules if presented (-coll_tuned_dynamic_rules_filename = rules)
|
|
|
|
* Else
|
|
|
|
* use forced rules (-coll_tuned_dynamic_ALG_intra_algorithm = algorithm-number)
|
|
|
|
* Else
|
|
|
|
* use fixed (compiled) rule set (or nested ifs)
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
2005-11-07 01:05:50 +03:00
|
|
|
/*
|
|
|
|
* allreduce_intra
|
|
|
|
*
|
|
|
|
* Function: - allreduce using other MPI collectives
|
|
|
|
* Accepts: - same as MPI_Allreduce()
|
|
|
|
* Returns: - MPI_SUCCESS or error code
|
|
|
|
*/
|
|
|
|
int
|
2005-12-22 16:49:33 +03:00
|
|
|
ompi_coll_tuned_allreduce_intra_dec_dynamic (void *sbuf, void *rbuf, int count,
|
2006-10-18 06:00:46 +04:00
|
|
|
struct ompi_datatype_t *dtype,
|
|
|
|
struct ompi_op_t *op,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2005-11-07 01:05:50 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2005-11-07 01:05:50 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream, "ompi_coll_tuned_allreduce_intra_dec_dynamic"));
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2005-11-11 07:49:29 +03:00
|
|
|
/* check to see if we have some filebased rules */
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[ALLREDUCE]) {
|
2006-10-18 06:00:46 +04:00
|
|
|
/* we do, so calc the message size or what ever we need and use this for the evaluation */
|
2007-02-20 07:25:00 +03:00
|
|
|
int alg, faninout, segsize, ignoreme;
|
2006-10-18 00:20:58 +04:00
|
|
|
size_t dsize;
|
2005-11-11 07:49:29 +03:00
|
|
|
|
|
|
|
ompi_ddt_type_size (dtype, &dsize);
|
|
|
|
dsize *= count;
|
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[ALLREDUCE],
|
2007-02-20 07:25:00 +03:00
|
|
|
dsize, &faninout, &segsize, &ignoreme);
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for this message size */
|
|
|
|
return ompi_coll_tuned_allreduce_intra_do_this (sbuf, rbuf, count, dtype, op,
|
|
|
|
comm, module,
|
2006-10-18 06:00:46 +04:00
|
|
|
alg, faninout, segsize);
|
2005-11-11 07:49:29 +03:00
|
|
|
} /* found a method */
|
|
|
|
} /*end if any com rules to check */
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[ALLREDUCE].algorithm) {
|
|
|
|
return ompi_coll_tuned_allreduce_intra_do_forced (sbuf, rbuf, count, dtype, op,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_allreduce_intra_dec_fixed (sbuf, rbuf, count, dtype, op,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2006-12-21 21:40:02 +03:00
|
|
|
* alltoall_intra_dec
|
2005-11-07 01:05:50 +03:00
|
|
|
*
|
2006-12-21 21:40:02 +03:00
|
|
|
* Function: - seletects alltoall algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Alltoall()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from the bcast implementation)
|
2005-11-07 01:05:50 +03:00
|
|
|
*/
|
|
|
|
|
2005-12-22 16:49:33 +03:00
|
|
|
int ompi_coll_tuned_alltoall_intra_dec_dynamic(void *sbuf, int scount,
|
2006-10-18 06:00:46 +04:00
|
|
|
struct ompi_datatype_t *sdtype,
|
|
|
|
void* rbuf, int rcount,
|
|
|
|
struct ompi_datatype_t *rdtype,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2005-11-07 01:05:50 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2005-11-07 01:05:50 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream, "ompi_coll_tuned_alltoall_intra_dec_dynamic"));
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2005-11-11 07:49:29 +03:00
|
|
|
/* check to see if we have some filebased rules */
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[ALLTOALL]) {
|
2006-10-18 06:00:46 +04:00
|
|
|
/* we do, so calc the message size or what ever we need and use this for the evaluation */
|
2005-11-11 07:49:29 +03:00
|
|
|
int comsize;
|
2007-02-20 07:25:00 +03:00
|
|
|
int alg, faninout, segsize, max_requests;
|
2006-10-18 00:20:58 +04:00
|
|
|
size_t dsize;
|
2005-11-11 07:49:29 +03:00
|
|
|
|
|
|
|
ompi_ddt_type_size (sdtype, &dsize);
|
|
|
|
comsize = ompi_comm_size(comm);
|
|
|
|
dsize *= comsize * scount;
|
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[ALLTOALL],
|
2007-02-20 07:25:00 +03:00
|
|
|
dsize, &faninout, &segsize, &max_requests);
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for this message size */
|
|
|
|
return ompi_coll_tuned_alltoall_intra_do_this (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
comm, module,
|
2007-02-20 07:25:00 +03:00
|
|
|
alg, faninout, segsize, max_requests);
|
2005-11-11 07:49:29 +03:00
|
|
|
} /* found a method */
|
|
|
|
} /*end if any com rules to check */
|
|
|
|
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[ALLTOALL].algorithm) {
|
|
|
|
return ompi_coll_tuned_alltoall_intra_do_forced (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_alltoall_intra_dec_fixed (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
|
|
|
|
2008-05-07 06:31:24 +04:00
|
|
|
/*
|
|
|
|
* Function: - selects alltoallv algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Alltoallv()
|
|
|
|
* Returns: - MPI_SUCCESS or error code
|
|
|
|
*/
|
|
|
|
|
|
|
|
int ompi_coll_tuned_alltoallv_intra_dec_dynamic(void *sbuf, int *scounts, int *sdisps,
|
|
|
|
struct ompi_datatype_t *sdtype,
|
|
|
|
void* rbuf, int *rcounts, int *rdisps,
|
|
|
|
struct ompi_datatype_t *rdtype,
|
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
|
|
|
{
|
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream, "ompi_coll_tuned_alltoallv_intra_dec_dynamic"));
|
2008-05-07 06:31:24 +04:00
|
|
|
|
|
|
|
/*
|
|
|
|
* BEGIN - File Based Rules
|
|
|
|
*
|
|
|
|
* Here is where we would check to see if we have some file based
|
|
|
|
* rules. Currently, we do not, so move on to seeing if the user
|
|
|
|
* specified a specific algorithm. If not, then use the fixed
|
|
|
|
* decision code to decide.
|
|
|
|
*
|
|
|
|
* END - File Based Rules
|
|
|
|
*/
|
|
|
|
if (data->user_forced[ALLTOALLV].algorithm) {
|
|
|
|
return ompi_coll_tuned_alltoallv_intra_do_forced(sbuf, scounts, sdisps, sdtype,
|
|
|
|
rbuf, rcounts, rdisps, rdtype,
|
|
|
|
comm, module);
|
|
|
|
}
|
|
|
|
return ompi_coll_tuned_alltoallv_intra_dec_fixed(sbuf, scounts, sdisps, sdtype,
|
|
|
|
rbuf, rcounts, rdisps, rdtype,
|
|
|
|
comm, module);
|
|
|
|
}
|
|
|
|
|
2005-11-07 01:05:50 +03:00
|
|
|
/*
|
2006-12-21 21:40:02 +03:00
|
|
|
* barrier_intra_dec
|
2005-11-07 01:05:50 +03:00
|
|
|
*
|
2006-12-21 21:40:02 +03:00
|
|
|
* Function: - seletects barrier algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Barrier()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from the barrier implementation)
|
2005-11-07 01:05:50 +03:00
|
|
|
*/
|
2007-08-19 07:37:49 +04:00
|
|
|
int ompi_coll_tuned_barrier_intra_dec_dynamic(struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2005-11-07 01:05:50 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2005-11-07 01:05:50 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream,"ompi_coll_tuned_barrier_intra_dec_dynamic"));
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2005-11-11 07:49:29 +03:00
|
|
|
/* check to see if we have some filebased rules */
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[BARRIER]) {
|
2006-10-18 06:00:46 +04:00
|
|
|
/* we do, so calc the message size or what ever we need and use this for the evaluation */
|
2007-02-20 07:25:00 +03:00
|
|
|
int alg, faninout, segsize, ignoreme;
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[BARRIER],
|
2007-02-20 07:25:00 +03:00
|
|
|
0, &faninout, &segsize, &ignoreme);
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for this message size */
|
|
|
|
return ompi_coll_tuned_barrier_intra_do_this (comm, module,
|
2006-10-18 06:00:46 +04:00
|
|
|
alg, faninout, segsize);
|
2005-11-11 07:49:29 +03:00
|
|
|
} /* found a method */
|
|
|
|
} /*end if any com rules to check */
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[BARRIER].algorithm) {
|
|
|
|
return ompi_coll_tuned_barrier_intra_do_forced (comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_barrier_intra_dec_fixed (comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* bcast_intra_dec
|
|
|
|
*
|
|
|
|
* Function: - seletects broadcast algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Bcast()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from the bcast implementation)
|
|
|
|
*/
|
2005-12-22 16:49:33 +03:00
|
|
|
int ompi_coll_tuned_bcast_intra_dec_dynamic(void *buff, int count,
|
2006-10-18 06:00:46 +04:00
|
|
|
struct ompi_datatype_t *datatype, int root,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2005-11-07 01:05:50 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2005-11-07 01:05:50 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream, "coll:tuned:bcast_intra_dec_dynamic"));
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2005-11-11 07:49:29 +03:00
|
|
|
/* check to see if we have some filebased rules */
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[BCAST]) {
|
2006-10-18 06:00:46 +04:00
|
|
|
/* we do, so calc the message size or what ever we need and use this for the evaluation */
|
2007-02-20 07:25:00 +03:00
|
|
|
int alg, faninout, segsize, ignoreme;
|
2006-10-18 00:20:58 +04:00
|
|
|
size_t dsize;
|
2005-11-11 07:49:29 +03:00
|
|
|
|
|
|
|
ompi_ddt_type_size (datatype, &dsize);
|
|
|
|
dsize *= count;
|
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[BCAST],
|
2007-02-20 07:25:00 +03:00
|
|
|
dsize, &faninout, &segsize, &ignoreme);
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for this message size */
|
|
|
|
return ompi_coll_tuned_bcast_intra_do_this (buff, count, datatype, root,
|
|
|
|
comm, module,
|
2005-11-11 07:49:29 +03:00
|
|
|
alg, faninout, segsize);
|
|
|
|
} /* found a method */
|
|
|
|
} /*end if any com rules to check */
|
|
|
|
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[BCAST].algorithm) {
|
|
|
|
return ompi_coll_tuned_bcast_intra_do_forced (buff, count, datatype, root,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_bcast_intra_dec_fixed (buff, count, datatype, root,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2006-12-21 21:40:02 +03:00
|
|
|
* reduce_intra_dec
|
2005-11-07 01:05:50 +03:00
|
|
|
*
|
2006-12-21 21:40:02 +03:00
|
|
|
* Function: - seletects reduce algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_reduce()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from the reduce implementation)
|
2005-11-07 01:05:50 +03:00
|
|
|
*
|
|
|
|
*/
|
2005-12-22 16:49:33 +03:00
|
|
|
int ompi_coll_tuned_reduce_intra_dec_dynamic( void *sendbuf, void *recvbuf,
|
2006-10-18 06:00:46 +04:00
|
|
|
int count, struct ompi_datatype_t* datatype,
|
|
|
|
struct ompi_op_t* op, int root,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t* comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2005-11-07 01:05:50 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2005-11-07 01:05:50 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream, "coll:tuned:reduce_intra_dec_dynamic"));
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2005-11-11 07:49:29 +03:00
|
|
|
/* check to see if we have some filebased rules */
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[REDUCE]) {
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2006-10-18 06:00:46 +04:00
|
|
|
/* we do, so calc the message size or what ever we need and use this for the evaluation */
|
2007-04-26 00:39:53 +04:00
|
|
|
int alg, faninout, segsize, max_requests;
|
2006-10-18 00:20:58 +04:00
|
|
|
size_t dsize;
|
2005-11-11 07:49:29 +03:00
|
|
|
|
|
|
|
ompi_ddt_type_size (datatype, &dsize);
|
|
|
|
dsize *= count;
|
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[REDUCE],
|
2007-04-26 00:39:53 +04:00
|
|
|
dsize, &faninout, &segsize, &max_requests);
|
2005-11-11 07:49:29 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for this message size */
|
|
|
|
return ompi_coll_tuned_reduce_intra_do_this (sendbuf, recvbuf, count, datatype,
|
|
|
|
op, root,
|
|
|
|
comm, module,
|
2007-04-26 00:39:53 +04:00
|
|
|
alg, faninout,
|
|
|
|
segsize,
|
|
|
|
max_requests);
|
2005-11-11 07:49:29 +03:00
|
|
|
} /* found a method */
|
|
|
|
} /*end if any com rules to check */
|
2005-11-07 01:05:50 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[REDUCE].algorithm) {
|
|
|
|
return ompi_coll_tuned_reduce_intra_do_forced (sendbuf, recvbuf, count, datatype,
|
|
|
|
op, root,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_reduce_intra_dec_fixed (sendbuf, recvbuf, count, datatype,
|
|
|
|
op, root,
|
|
|
|
comm, module);
|
2005-11-07 01:05:50 +03:00
|
|
|
}
|
|
|
|
|
2007-03-05 23:40:39 +03:00
|
|
|
/*
|
|
|
|
* reduce_scatter_intra_dec
|
|
|
|
*
|
|
|
|
* Function: - seletects reduce_scatter algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Reduce_scatter()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from
|
|
|
|
* the reduce_scatter implementation)
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
int ompi_coll_tuned_reduce_scatter_intra_dec_dynamic(void *sbuf, void *rbuf,
|
|
|
|
int *rcounts,
|
|
|
|
struct ompi_datatype_t *dtype,
|
|
|
|
struct ompi_op_t *op,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2007-03-05 23:40:39 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2007-03-05 23:40:39 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream, "coll:tuned:reduce_scatter_intra_dec_dynamic"));
|
2007-03-05 23:40:39 +03:00
|
|
|
|
|
|
|
/* check to see if we have some filebased rules */
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[REDUCESCATTER]) {
|
2007-03-05 23:40:39 +03:00
|
|
|
/* we do, so calc the message size or what ever we need and use
|
|
|
|
this for the evaluation */
|
|
|
|
int alg, faninout, segsize, ignoreme, i, count, size;
|
|
|
|
size_t dsize;
|
|
|
|
size = ompi_comm_size(comm);
|
|
|
|
for (i = 0, count = 0; i < size; i++) { count += rcounts[i];}
|
|
|
|
ompi_ddt_type_size (dtype, &dsize);
|
|
|
|
dsize *= count;
|
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[REDUCESCATTER],
|
2007-03-05 23:40:39 +03:00
|
|
|
dsize, &faninout,
|
|
|
|
&segsize, &ignoreme);
|
|
|
|
if (alg) {
|
2007-08-19 07:37:49 +04:00
|
|
|
/* we have found a valid choice from the file based rules for this message size */
|
|
|
|
return ompi_coll_tuned_reduce_scatter_intra_do_this (sbuf, rbuf, rcounts,
|
|
|
|
dtype, op,
|
|
|
|
comm, module,
|
2007-03-05 23:40:39 +03:00
|
|
|
alg, faninout,
|
|
|
|
segsize);
|
|
|
|
} /* found a method */
|
|
|
|
} /*end if any com rules to check */
|
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[REDUCESCATTER].algorithm) {
|
|
|
|
return ompi_coll_tuned_reduce_scatter_intra_do_forced (sbuf, rbuf, rcounts,
|
|
|
|
dtype, op,
|
|
|
|
comm, module);
|
2007-03-05 23:40:39 +03:00
|
|
|
}
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_reduce_scatter_intra_dec_fixed (sbuf, rbuf, rcounts,
|
|
|
|
dtype, op,
|
|
|
|
comm, module);
|
2007-03-05 23:40:39 +03:00
|
|
|
}
|
|
|
|
|
2006-12-21 21:40:02 +03:00
|
|
|
/*
|
|
|
|
* allgather_intra_dec
|
|
|
|
*
|
|
|
|
* Function: - seletects allgather algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Allgather()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from the selected
|
|
|
|
* allgather function).
|
|
|
|
*/
|
|
|
|
|
|
|
|
int ompi_coll_tuned_allgather_intra_dec_dynamic(void *sbuf, int scount,
|
|
|
|
struct ompi_datatype_t *sdtype,
|
|
|
|
void* rbuf, int rcount,
|
|
|
|
struct ompi_datatype_t *rdtype,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2006-12-21 21:40:02 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream,
|
2007-08-19 07:37:49 +04:00
|
|
|
"ompi_coll_tuned_allgather_intra_dec_dynamic"));
|
2006-12-21 21:40:02 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[ALLGATHER]) {
|
|
|
|
/* We have file based rules:
|
|
|
|
- calculate message size and other necessary information */
|
|
|
|
int comsize;
|
|
|
|
int alg, faninout, segsize, ignoreme;
|
|
|
|
size_t dsize;
|
2006-12-21 21:40:02 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
ompi_ddt_type_size (sdtype, &dsize);
|
|
|
|
comsize = ompi_comm_size(comm);
|
|
|
|
dsize *= comsize * scount;
|
2006-12-21 21:40:02 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[ALLGATHER],
|
|
|
|
dsize, &faninout, &segsize, &ignoreme);
|
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for
|
|
|
|
this message size */
|
|
|
|
return ompi_coll_tuned_allgather_intra_do_this (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
comm, module,
|
|
|
|
alg, faninout, segsize);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* We do not have file based rules */
|
|
|
|
if (data->user_forced[ALLGATHER].algorithm) {
|
|
|
|
/* User-forced algorithm */
|
|
|
|
return ompi_coll_tuned_allgather_intra_do_forced (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
comm, module);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Use default decision */
|
|
|
|
return ompi_coll_tuned_allgather_intra_dec_fixed (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
comm, module);
|
2006-12-21 21:40:02 +03:00
|
|
|
}
|
|
|
|
|
2007-07-04 03:33:12 +04:00
|
|
|
/*
|
|
|
|
* allgatherv_intra_dec
|
|
|
|
*
|
|
|
|
* Function: - seletects allgatherv algorithm to use
|
|
|
|
* Accepts: - same arguments as MPI_Allgatherv()
|
|
|
|
* Returns: - MPI_SUCCESS or error code (passed from the selected
|
|
|
|
* allgatherv function).
|
|
|
|
*/
|
|
|
|
|
|
|
|
int ompi_coll_tuned_allgatherv_intra_dec_dynamic(void *sbuf, int scount,
|
|
|
|
struct ompi_datatype_t *sdtype,
|
|
|
|
void* rbuf, int *rcounts,
|
|
|
|
int *rdispls,
|
|
|
|
struct ompi_datatype_t *rdtype,
|
2007-08-19 07:37:49 +04:00
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2007-07-04 03:33:12 +04:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2007-07-04 03:33:12 +04:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream,
|
2007-08-19 07:37:49 +04:00
|
|
|
"ompi_coll_tuned_allgatherv_intra_dec_dynamic"));
|
2007-07-04 03:33:12 +04:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->com_rules[ALLGATHERV]) {
|
|
|
|
/* We have file based rules:
|
|
|
|
- calculate message size and other necessary information */
|
|
|
|
int comsize, i;
|
|
|
|
int alg, faninout, segsize, ignoreme;
|
|
|
|
size_t dsize, total_size;
|
|
|
|
|
|
|
|
comsize = ompi_comm_size(comm);
|
|
|
|
ompi_ddt_type_size (sdtype, &dsize);
|
|
|
|
total_size = 0;
|
|
|
|
for (i = 0; i < comsize; i++) { total_size += dsize * rcounts[i]; }
|
2007-07-04 03:33:12 +04:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
alg = ompi_coll_tuned_get_target_method_params (data->com_rules[ALLGATHERV],
|
|
|
|
total_size, &faninout, &segsize, &ignoreme);
|
|
|
|
if (alg) {
|
|
|
|
/* we have found a valid choice from the file based rules for
|
|
|
|
this message size */
|
|
|
|
return ompi_coll_tuned_allgatherv_intra_do_this (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcounts,
|
|
|
|
rdispls, rdtype,
|
|
|
|
comm, module,
|
|
|
|
alg, faninout, segsize);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* We do not have file based rules */
|
|
|
|
if (data->user_forced[ALLGATHERV].algorithm) {
|
|
|
|
/* User-forced algorithm */
|
|
|
|
return ompi_coll_tuned_allgatherv_intra_do_forced (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcounts,
|
|
|
|
rdispls, rdtype,
|
|
|
|
comm, module);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Use default decision */
|
|
|
|
return ompi_coll_tuned_allgatherv_intra_dec_fixed (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcounts,
|
|
|
|
rdispls, rdtype,
|
|
|
|
comm, module);
|
2007-07-04 03:33:12 +04:00
|
|
|
}
|
|
|
|
|
2007-02-28 04:11:01 +03:00
|
|
|
int ompi_coll_tuned_gather_intra_dec_dynamic(void *sbuf, int scount,
|
|
|
|
struct ompi_datatype_t *sdtype,
|
|
|
|
void* rbuf, int rcount,
|
|
|
|
struct ompi_datatype_t *rdtype,
|
2007-08-19 07:37:49 +04:00
|
|
|
int root,
|
|
|
|
struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2007-02-28 04:11:01 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2007-02-28 04:11:01 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream,
|
2007-08-19 07:37:49 +04:00
|
|
|
"ompi_coll_tuned_gather_intra_dec_dynamic"));
|
2007-02-28 04:11:01 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[GATHER].algorithm) {
|
|
|
|
return ompi_coll_tuned_gather_intra_do_forced (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
root, comm, module);
|
|
|
|
}
|
2007-02-28 04:11:01 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_gather_intra_dec_fixed (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
root, comm, module);
|
2007-02-28 04:11:01 +03:00
|
|
|
}
|
2007-03-03 02:19:02 +03:00
|
|
|
|
|
|
|
int ompi_coll_tuned_scatter_intra_dec_dynamic(void *sbuf, int scount,
|
|
|
|
struct ompi_datatype_t *sdtype,
|
|
|
|
void* rbuf, int rcount,
|
|
|
|
struct ompi_datatype_t *rdtype,
|
2007-08-19 07:37:49 +04:00
|
|
|
int root, struct ompi_communicator_t *comm,
|
|
|
|
struct mca_coll_base_module_1_1_0_t *module)
|
2007-03-03 02:19:02 +03:00
|
|
|
{
|
2007-08-19 07:37:49 +04:00
|
|
|
mca_coll_tuned_module_t *tuned_module = (mca_coll_tuned_module_t*) module;
|
|
|
|
mca_coll_tuned_comm_t *data = tuned_module->tuned_data;
|
2007-03-03 02:19:02 +03:00
|
|
|
|
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_OUTPUT((ompi_coll_tuned_stream,
|
2007-08-19 07:37:49 +04:00
|
|
|
"ompi_coll_tuned_scatter_intra_dec_dynamic"));
|
2007-03-03 02:19:02 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
if (data->user_forced[SCATTER].algorithm) {
|
|
|
|
return ompi_coll_tuned_scatter_intra_do_forced (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
root, comm, module);
|
|
|
|
}
|
2007-03-03 02:19:02 +03:00
|
|
|
|
2007-08-19 07:37:49 +04:00
|
|
|
return ompi_coll_tuned_scatter_intra_dec_fixed (sbuf, scount, sdtype,
|
|
|
|
rbuf, rcount, rdtype,
|
|
|
|
root, comm, module);
|
2007-03-03 02:19:02 +03:00
|
|
|
}
|