Ralph Castain c693d3a5d1 I hadn't honestly considered before that an MPI process might attempt to call functions in the routed framework intended solely for daemons and HNPs. By design, MPI processes are not allowed to route RML/OOB messages, and hence the routed module in an MPI process has no knowledge whatsoever of how a message will reach its destination (except in the direct module). Thus, it has no way to return a valid routing tree, update a routing tree, or get wireup info. ...

This commit ensures that attempts to access information that is unknowable or undefined returns appropriate invalid or not_supported values to avoid unexpected behavior and/or segfaults.

This commit was SVN r18692.

2008-06-20 03:26:13 +00:00

..

configure.params

Rename the routed modules to more accurately reflect what they do and the role they will play in soon-to-come updates.

2008-05-05 02:59:09 +00:00

Makefile.am

Rename the routed modules to more accurately reflect what they do and the role they will play in soon-to-come updates.

2008-05-05 02:59:09 +00:00

routed_direct_component.c

Merge in the mca_base_select changes per RFC:

2008-05-06 18:08:45 +00:00

routed_direct.c

I hadn't honestly considered before that an MPI process might attempt to call functions in the routed framework intended solely for daemons and HNPs. By design, MPI processes are not allowed to route RML/OOB messages, and hence the routed module in an MPI process has no knowledge whatsoever of how a message will reach its destination (except in the direct module). Thus, it has no way to return a valid routing tree, update a routing tree, or get wireup info.

2008-06-20 03:26:13 +00:00

routed_direct.h

Rename the routed modules to more accurately reflect what they do and the role they will play in soon-to-come updates.

2008-05-05 02:59:09 +00:00