2004-12-21 22:16:09 +00:00
/*
2007-03-16 23:11:45 +00:00
* Copyright ( c ) 2004 - 2007 The Trustees of Indiana University and Indiana
2005-11-05 19:57:48 +00: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 .
2004-12-21 22:16:09 +00:00
* Copyright ( c ) 2004 - 2005 High Performance Computing Center Stuttgart ,
* University of Stuttgart . All rights reserved .
2005-03-24 12:43:37 +00:00
* Copyright ( c ) 2004 - 2005 The Regents of the University of California .
* All rights reserved .
2007-06-08 22:59:31 +00:00
* Copyright ( c ) 2007 Cisco , Inc . All rights reserved .
2004-12-21 22:16:09 +00:00
* $ COPYRIGHT $
*
* Additional copyrights may follow
*
* $ HEADER $
*/
2007-06-08 22:59:31 +00:00
2006-02-12 01:33:29 +00:00
# include "orte_config.h"
2008-02-28 01:57:57 +00:00
# include "orte/constants.h"
2007-06-08 22:59:31 +00:00
2004-12-21 22:16:09 +00:00
# include <errno.h>
2005-12-12 20:04:00 +00:00
# ifdef HAVE_UNISTD_H
2004-12-21 22:16:09 +00:00
# include <unistd.h>
2005-12-12 20:04:00 +00:00
# endif /* HAVE_UNISTD_H */
# ifdef HAVE_STRING_H
2004-12-21 22:16:09 +00:00
# include <string.h>
2005-12-12 20:04:00 +00:00
# endif /* HAVE_STRING_H */
2004-12-21 22:16:09 +00: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-13 20:00:55 +00:00
# include "orte/util/output.h"
2008-02-28 01:57:57 +00:00
2006-02-12 01:33:29 +00:00
# include "orte/mca/iof/iof.h"
# include "orte/mca/rml/rml.h"
# include "orte/mca/rml/rml_types.h"
2008-02-28 01:57:57 +00:00
# include "orte/mca/errmgr/errmgr.h"
# include "orte/util/name_fns.h"
# include "orte/runtime/orte_globals.h"
2006-02-12 01:33:29 +00:00
# include "orte/mca/iof/iof.h"
# include "orte/mca/iof/base/base.h"
# include "orte/mca/iof/base/iof_base_endpoint.h"
2008-02-28 01:57:57 +00:00
2004-12-21 22:16:09 +00:00
# include "iof_proxy.h"
2005-01-12 20:51:34 +00:00
# include "iof_proxy_svc.h"
2004-12-21 22:16:09 +00:00
2005-03-14 20:57:21 +00:00
orte_iof_base_module_t orte_iof_proxy_module = {
orte_iof_proxy_publish ,
orte_iof_proxy_unpublish ,
orte_iof_proxy_subscribe ,
orte_iof_proxy_unsubscribe ,
2007-06-08 22:59:31 +00:00
orte_iof_proxy_push ,
orte_iof_proxy_pull ,
2007-01-30 06:34:38 +00:00
orte_iof_base_flush ,
2007-03-16 23:11:45 +00:00
orte_iof_proxy_finalize ,
orte_iof_proxy_ft_event
2004-12-21 22:16:09 +00:00
} ;
2007-06-08 22:59:31 +00:00
/*
* Finalize module ; nothing to do
*/
int orte_iof_proxy_finalize ( void )
{
2007-03-16 23:11:45 +00:00
return ORTE_SUCCESS ;
}
2004-12-21 22:16:09 +00:00
/**
2007-06-08 22:59:31 +00:00
* Create an endpoint for a local file descriptor and " publish " it
* under the name of the origin process . If the publish mode is a
* SINK , then create a publication entry for it so that incoming
* messages can be forwarded to it .
2004-12-21 22:16:09 +00:00
*
2007-06-08 22:59:31 +00:00
* SOURCEs do not need to create publication records because a ) the
* endpoint will automatically wake up the event engine and read off
* the fd whenever there is data available , and b ) this data is then
* automatically sent to the iof svc component for possible
* forwarding .
2004-12-21 22:16:09 +00:00
*/
2005-03-14 20:57:21 +00:00
int orte_iof_proxy_publish (
2007-06-08 22:59:31 +00:00
const orte_process_name_t * origin ,
2005-03-14 20:57:21 +00:00
orte_iof_base_mode_t mode ,
orte_iof_base_tag_t tag ,
2004-12-21 22:16:09 +00:00
int fd )
{
2005-01-12 20:51:34 +00:00
int rc ;
2007-06-08 22:59:31 +00:00
if ( orte_iof_base . iof_output > = 0 ) {
2005-03-14 20:57:21 +00:00
char * name_str ;
2008-02-28 01:57:57 +00:00
orte_util_convert_process_name_to_string ( & name_str , origin ) ;
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-13 20:00:55 +00:00
orte_output_verbose ( 1 , orte_iof_base . iof_output ,
2007-06-08 22:59:31 +00:00
" orte_iof_proxy_publish(%s,%d,%d,%d) \n " ,
name_str , mode , tag , fd ) ;
2005-03-14 20:57:21 +00:00
free ( name_str ) ;
}
rc = orte_iof_base_endpoint_create (
2007-06-08 22:59:31 +00:00
origin ,
2005-01-12 20:51:34 +00:00
mode ,
tag ,
fd ) ;
2007-06-08 22:59:31 +00:00
if ( ORTE_SUCCESS ! = rc ) {
return rc ;
}
/* publish to server */
if ( ORTE_IOF_SINK = = mode ) {
rc = orte_iof_proxy_svc_publish ( origin , tag ) ;
if ( rc ! = ORTE_SUCCESS ) {
return rc ;
}
}
return ORTE_SUCCESS ;
2004-12-21 22:16:09 +00:00
}
/**
2007-06-08 22:59:31 +00:00
* Remove all registrations matching the specified origin process
2004-12-21 22:16:09 +00:00
* name , mask and tag values .
*/
2005-03-14 20:57:21 +00:00
int orte_iof_proxy_unpublish (
2007-06-08 22:59:31 +00:00
const orte_process_name_t * origin ,
2005-03-14 20:57:21 +00:00
orte_ns_cmp_bitmask_t mask ,
orte_iof_base_tag_t tag )
2004-12-21 22:16:09 +00:00
{
2005-01-12 20:51:34 +00:00
int rc ;
2007-06-08 22:59:31 +00:00
#if 0
{
int i = 0 ;
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-13 20:00:55 +00:00
orte_output_verbose ( 1 , orte_iof_base . iof_output , " %s orted: ******** ABOUT TO IOF PROXY UNPUBLISH, %d " , ORTE_NAME_PRINT ( orte_process_info . my_name ) , getpid ( ) ) ;
2007-06-08 22:59:31 +00:00
fflush ( stderr ) ;
while ( 0 = = i ) sleep ( 5 ) ;
}
# endif
2005-01-12 20:51:34 +00:00
/* cleanup server */
2005-03-14 20:57:21 +00:00
orte_iof_proxy_svc_unpublish (
2007-06-08 22:59:31 +00:00
origin ,
2005-01-12 20:51:34 +00:00
mask ,
tag ) ;
2007-07-12 19:53:18 +00:00
/* delete local endpoint. Note that the endpoint may have already
been deleted ( e . g . , if some entity noticed that the fd closed
and called orte_iof_base_endpoint_delete on the corresopnding
endpoint already ) . So if we get NOT_FOUND , ignore that error
- - the end result is what we want : the endpoint is deleted when
we return . */
2005-03-14 20:57:21 +00:00
rc = orte_iof_base_endpoint_delete (
2007-06-08 22:59:31 +00:00
origin ,
2005-01-12 20:51:34 +00:00
mask ,
tag ) ;
2007-07-12 19:53:18 +00:00
if ( ORTE_ERR_NOT_FOUND = = rc | | ORTE_SUCCESS = = rc ) {
return ORTE_SUCCESS ;
} else {
return rc ;
}
2004-12-21 22:16:09 +00:00
}
/**
* Explicitly push data from the specified file descriptor
2007-06-08 22:59:31 +00:00
* to the indicated SINK set of peers .
2004-12-21 22:16:09 +00:00
*/
2005-03-14 20:57:21 +00:00
int orte_iof_proxy_push (
2007-06-08 22:59:31 +00:00
const orte_process_name_t * sink_name ,
orte_ns_cmp_bitmask_t sink_mask ,
orte_iof_base_tag_t sink_tag ,
2004-12-21 22:16:09 +00:00
int fd )
{
2005-01-12 20:51:34 +00:00
int rc ;
2007-06-08 22:59:31 +00:00
/* setup a local endpoint to reflect registration. Do this before
we send the subscription to the server in case a callback
occurs * while * we are sending the subscription request . */
2005-03-14 20:57:21 +00:00
rc = orte_iof_base_endpoint_create (
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
ORTE_PROC_MY_NAME ,
2005-03-14 20:57:21 +00:00
ORTE_IOF_SOURCE ,
2007-06-08 22:59:31 +00:00
sink_tag ,
2005-01-12 20:51:34 +00:00
fd ) ;
2007-06-08 22:59:31 +00:00
if ( ORTE_SUCCESS ! = rc ) {
return rc ;
}
/* send a subscription to server on behalf of the destination */
rc = orte_iof_proxy_svc_subscribe (
ORTE_PROC_MY_NAME ,
ORTE_NS_CMP_ALL ,
sink_tag ,
sink_name ,
sink_mask ,
sink_tag
) ;
return rc ;
2004-12-21 22:16:09 +00:00
}
/**
2007-06-08 22:59:31 +00:00
* Explicitly pull data from the specified set of SOURCE peers and
* dump to the indicated file descriptor .
2004-12-21 22:16:09 +00:00
*/
2005-03-14 20:57:21 +00:00
int orte_iof_proxy_pull (
2007-06-08 22:59:31 +00:00
const orte_process_name_t * source_name ,
orte_ns_cmp_bitmask_t source_mask ,
orte_iof_base_tag_t source_tag ,
2004-12-21 22:16:09 +00:00
int fd )
{
2005-01-12 20:51:34 +00:00
/* setup a local endpoint */
int rc ;
2005-03-14 20:57:21 +00:00
rc = orte_iof_base_endpoint_create (
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
ORTE_PROC_MY_NAME ,
2005-03-29 19:40:38 +00:00
ORTE_IOF_SINK ,
2007-06-08 22:59:31 +00:00
source_tag ,
2005-01-12 20:51:34 +00:00
fd ) ;
2007-06-08 22:59:31 +00:00
if ( ORTE_SUCCESS ! = rc ) {
2005-03-29 19:40:38 +00:00
ORTE_ERROR_LOG ( rc ) ;
2005-01-12 20:51:34 +00:00
return rc ;
2005-03-29 19:40:38 +00:00
}
2005-01-12 20:51:34 +00:00
2005-03-29 19:40:38 +00:00
/* publish this endpoint */
rc = orte_iof_proxy_svc_publish (
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
ORTE_PROC_MY_NAME ,
2007-06-08 22:59:31 +00:00
source_tag ) ;
if ( ORTE_SUCCESS ! = rc ) {
2005-03-29 19:40:38 +00:00
ORTE_ERROR_LOG ( rc ) ;
return rc ;
}
/* subscribe to peer */
2005-03-14 20:57:21 +00:00
rc = orte_iof_proxy_svc_subscribe (
2007-06-08 22:59:31 +00:00
source_name ,
source_mask ,
source_tag ,
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
ORTE_PROC_MY_NAME ,
2005-03-14 20:57:21 +00:00
ORTE_NS_CMP_ALL ,
2007-06-08 22:59:31 +00:00
source_tag ) ;
if ( ORTE_SUCCESS ! = rc ) {
2005-03-29 19:40:38 +00:00
ORTE_ERROR_LOG ( rc ) ;
return rc ;
}
2005-01-12 20:51:34 +00:00
return rc ;
2004-12-21 22:16:09 +00:00
}
/*
* Subscribe to receive a callback on receipt of data
2007-06-08 22:59:31 +00:00
* from a specified set of origin peers .
2004-12-21 22:16:09 +00:00
*/
2005-03-14 20:57:21 +00:00
int orte_iof_proxy_subscribe (
2007-06-08 22:59:31 +00:00
const orte_process_name_t * origin_name ,
orte_ns_cmp_bitmask_t origin_mask ,
orte_iof_base_tag_t origin_tag ,
2005-11-10 04:49:51 +00:00
orte_iof_base_callback_fn_t cbfunc ,
2004-12-21 22:16:09 +00:00
void * cbdata )
{
2005-01-12 20:51:34 +00:00
int rc ;
/* create a local registration to reflect the callback */
2007-06-08 22:59:31 +00:00
rc = orte_iof_base_callback_create ( ORTE_PROC_MY_NAME , origin_tag , cbfunc , cbdata ) ;
if ( ORTE_SUCCESS ! = rc ) {
2005-11-10 04:49:51 +00:00
return rc ;
2007-06-08 22:59:31 +00:00
}
2005-01-12 20:51:34 +00:00
/* send a subscription message to the service */
2005-03-14 20:57:21 +00:00
rc = orte_iof_proxy_svc_subscribe (
2007-06-08 22:59:31 +00:00
origin_name ,
origin_mask ,
origin_tag ,
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
ORTE_PROC_MY_NAME ,
2005-03-14 20:57:21 +00:00
ORTE_NS_CMP_ALL ,
2007-06-08 22:59:31 +00:00
origin_tag ) ;
2005-01-12 20:51:34 +00:00
return rc ;
2004-12-21 22:16:09 +00:00
}
2007-06-08 22:59:31 +00:00
/*
* Remove a subscription
*/
2005-03-14 20:57:21 +00:00
int orte_iof_proxy_unsubscribe (
2007-06-08 22:59:31 +00:00
const orte_process_name_t * origin_name ,
orte_ns_cmp_bitmask_t origin_mask ,
orte_iof_base_tag_t origin_tag )
2004-12-21 22:16:09 +00:00
{
2005-01-12 20:51:34 +00:00
int rc ;
/* send an unsubscribe message to the service */
2005-03-14 20:57:21 +00:00
rc = orte_iof_proxy_svc_unsubscribe (
2007-06-08 22:59:31 +00:00
origin_name ,
origin_mask ,
origin_tag ,
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
ORTE_PROC_MY_NAME ,
2005-03-14 20:57:21 +00:00
ORTE_NS_CMP_ALL ,
2007-06-08 22:59:31 +00:00
origin_tag ) ;
if ( ORTE_SUCCESS ! = rc ) {
2005-11-10 04:49:51 +00:00
return rc ;
2007-06-08 22:59:31 +00:00
}
2005-11-10 04:49:51 +00:00
2005-01-12 20:51:34 +00:00
/* remove local callback */
2007-06-08 22:59:31 +00:00
return orte_iof_base_callback_delete ( ORTE_PROC_MY_NAME , origin_tag ) ;
2004-12-21 22:16:09 +00:00
}
2007-06-08 22:59:31 +00:00
/*
* FT event
*/
2007-03-16 23:11:45 +00:00
int orte_iof_proxy_ft_event ( int state ) {
int ret , exit_status = ORTE_SUCCESS ;
if ( OPAL_CRS_CHECKPOINT = = state ) {
/*
* Flush
*/
if ( ORTE_SUCCESS ! = ( ret = orte_iof_base_flush ( ) ) ) {
return ret ;
}
/*
* Stop receiving events
*/
orte_rml . recv_cancel ( ORTE_NAME_WILDCARD , ORTE_RML_TAG_IOF_SVC ) ;
}
else if ( OPAL_CRS_CONTINUE = = state ) {
/*
* Restart Receiving events
*/
if ( ORTE_SUCCESS ! = ( ret = orte_rml . recv_nb (
ORTE_NAME_WILDCARD ,
mca_iof_proxy_component . proxy_iov ,
1 ,
ORTE_RML_TAG_IOF_SVC ,
ORTE_RML_ALLOC | ORTE_RML_PERSISTENT ,
orte_iof_proxy_svc_recv ,
NULL
) ) ) {
exit_status = ret ;
goto cleanup ;
}
}
else if ( OPAL_CRS_RESTART = = state ) {
/*
* Restart Receiving events
*/
if ( ORTE_SUCCESS ! = ( ret = orte_rml . recv_nb (
ORTE_NAME_WILDCARD ,
mca_iof_proxy_component . proxy_iov ,
1 ,
ORTE_RML_TAG_IOF_SVC ,
ORTE_RML_ALLOC | ORTE_RML_PERSISTENT ,
orte_iof_proxy_svc_recv ,
NULL
) ) ) {
exit_status = ret ;
goto cleanup ;
}
}
else if ( OPAL_CRS_TERM = = state ) {
;
}
else {
;
}
cleanup :
return exit_status ;
}