Ralph Castain 9902748108 ***** THIS INCLUDES A SMALL CHANGE IN THE MPI-RTE INTERFACE ***** ... Fix two problems that surfaced when using direct launch under SLURM: 1. locally store our own data because some BTLs want to retrieve it during add_procs rather than use what they have internally 2. cleanup MPI_Abort so it correctly passes the error status all the way down to the actual exit. When someone implemented the "abort_peers" API, they left out the error status. So we lost it at that point and *always* exited with a status of 1. This forces a change to the API to include the status. cmr:v1.7.3:reviewer=jsquyres:subject=Fix MPI_Abort and modex_recv for direct launch This commit was SVN r29405.		2013-10-08 18:37:59 +00:00
..
base	As per the RFC, bring in the ORTE async progress code and the rewrite of OOB:	2013-08-22 16:37:40 +00:00
orte	***** THIS INCLUDES A SMALL CHANGE IN THE MPI-RTE INTERFACE *****	2013-10-08 18:37:59 +00:00
pmi	***** THIS INCLUDES A SMALL CHANGE IN THE MPI-RTE INTERFACE *****	2013-10-08 18:37:59 +00:00
configure.m4	Move the RTE framework change into the trunk. With this change, all non-CR	2013-01-27 23:25:10 +00:00
Makefile.am	Move the RTE framework change into the trunk. With this change, all non-CR	2013-01-27 23:25:10 +00:00
rte.h	Do some cleanup of the way we handle modex data. Identify data that needs to be shared with peers in my job vs data that needs to be shared with non-peers - no point in sharing extra data. When we share data with some process(es) from another job, we cannot know in advance what info they have or lack, so we have to share everything just in case. This limits the optimization we can do for things like comm_spawn.	2013-09-27 00:37:49 +00:00