1
1
openmpi/orte/mca
Ralph Castain 9f97c74ba3 Silence warning
This commit was SVN r32136.
2014-07-03 17:29:04 +00:00
..
dfs The final step of the RFC: convert the <foo>libdir and friends to fit their respective code areas, and equate them all at the top. Note that we can't entirely separate things as the opal_install_dirs framework can't handle separated locations for the various trees. 2014-05-08 02:01:35 +00:00
errmgr Remove a potential race condition - we'll cleanup the local children when we are all done 2014-07-03 14:13:43 +00:00
ess get the FT code to compile again by adding/removing #includes 2014-06-25 18:42:17 +00:00
filem This isn't as big a change as it appears - a change in one place caused a whole bunch of files to require updated #include's due to some arcane linkage. Rework the orte_wait code to reflect the introduction of the state machine. If we are in cleanup mode and just want to kill all our local children, then there is no reason to be polite about it as that introduces *very* long delays at scale. Just kill the procs and move on. 2014-06-17 17:57:51 +00:00
grpcomm Cleanup a memory leak in the daemons - thanks to Artem for spotting it 2014-06-09 17:14:02 +00:00
iof This isn't as big a change as it appears - a change in one place caused a whole bunch of files to require updated #include's due to some arcane linkage. Rework the orte_wait code to reflect the introduction of the state machine. If we are in cleanup mode and just want to kill all our local children, then there is no reason to be polite about it as that introduces *very* long delays at scale. Just kill the procs and move on. 2014-06-17 17:57:51 +00:00
odls Move all collective id's into the attributes and let the job pack/unpack take care of them instead of singling them out. Add the envars just prior to forking the children instead of into the launch message itself. Remove a few #if CR as the attributes functionality can handle this condition now. 2014-07-03 15:58:13 +00:00
oob Revert r32082 and r32070 - the developer's conference has decided to go a different direction on the threaded progress effort. This will involve some degree of prototyping to understand the tradeoffs prior to making a final design decision, and so we'll hold off on the final change until that is completed. 2014-06-25 20:43:28 +00:00
plm Move all collective id's into the attributes and let the job pack/unpack take care of them instead of singling them out. Add the envars just prior to forking the children instead of into the launch message itself. Remove a few #if CR as the attributes functionality can handle this condition now. 2014-07-03 15:58:13 +00:00
ras Silence warning 2014-07-03 17:29:04 +00:00
rmaps Per request from Jeff, slightly modify the show_help message as the precise name of the NUMA-containing packages differs based on OS and distro 2014-07-02 14:46:00 +00:00
rml This isn't as big a change as it appears - a change in one place caused a whole bunch of files to require updated #include's due to some arcane linkage. Rework the orte_wait code to reflect the introduction of the state machine. If we are in cleanup mode and just want to kill all our local children, then there is no reason to be polite about it as that introduces *very* long delays at scale. Just kill the procs and move on. 2014-06-17 17:57:51 +00:00
routed This isn't as big a change as it appears - a change in one place caused a whole bunch of files to require updated #include's due to some arcane linkage. Rework the orte_wait code to reflect the introduction of the state machine. If we are in cleanup mode and just want to kill all our local children, then there is no reason to be polite about it as that introduces *very* long delays at scale. Just kill the procs and move on. 2014-06-17 17:57:51 +00:00
rtc Fix static builds by renaming conflicting type 2014-06-14 17:39:28 +00:00
snapc use the orte attributes in the FT code to fix compile errors 2014-06-26 03:19:17 +00:00
sstore use the orte attributes in the FT code to fix compile errors 2014-06-26 03:19:17 +00:00
state Resolve the MTT timeout problem. This appears to have largely been caused by missing sigchld notifications, thus causing the daemons to believe that not all procs had exited. Let comm failure also serve as notification of process termination, and add appropriate flags/attributes to avoid multiple reporting of proc termination. 2014-06-21 17:09:02 +00:00