1
1
openmpi/orte/mca
2013-10-26 00:47:14 +00:00
..
dfs As per the RFC, bring in the ORTE async progress code and the rewrite of OOB: 2013-08-22 16:37:40 +00:00
errmgr ***** THIS INCLUDES A SMALL CHANGE IN THE MPI-RTE INTERFACE ***** 2013-10-08 18:37:59 +00:00
ess Initialize orte_coprocessors hash table to NULL. Delay coprocessor detection on HNP until after node topology final definition in case rmaps changes it. Minor spacing change. 2013-10-24 00:08:47 +00:00
filem As per the RFC, bring in the ORTE async progress code and the rewrite of OOB: 2013-08-22 16:37:40 +00:00
grpcomm **************************************************************** 2013-10-14 16:52:58 +00:00
iof The function orte_iof_base_setup_prefork attempts to create a pty for 2013-09-15 15:33:51 +00:00
odls Singletons currently start out by spawning an HNP - this is required solely in the cases where the singleton subsequently calls MPI_Comm_spawn or publishes port info without support from an external orte-server. In all other cases, the HNP is of no value and can actually be a detriment by creating additional overhead on the node. This is particularly concerning for async operations where processes may begin as singletons and then dynamically wireup to perform pt2pt communications. 2013-10-04 02:58:26 +00:00
oob Correct a bug in handling of oob_tcp_if_include/exclude addresses by using the kernel index instead of the raw index of the interface. 2013-10-26 00:47:14 +00:00
plm Initialize orte_coprocessors hash table to NULL. Delay coprocessor detection on HNP until after node topology final definition in case rmaps changes it. Minor spacing change. 2013-10-24 00:08:47 +00:00
ras As per the RFC, bring in the ORTE async progress code and the rewrite of OOB: 2013-08-22 16:37:40 +00:00
rmaps Do some cleanup of the --without-hwloc build - no need to work on coprocessors since we can't detect them anyway, cleanup some unused variables in the ppr mapper 2013-10-23 01:45:21 +00:00
rml Revert r29166 in favor of a better solution from George 2013-09-18 01:41:26 +00:00
routed Singletons currently start out by spawning an HNP - this is required solely in the cases where the singleton subsequently calls MPI_Comm_spawn or publishes port info without support from an external orte-server. In all other cases, the HNP is of no value and can actually be a detriment by creating additional overhead on the node. This is particularly concerning for async operations where processes may begin as singletons and then dynamically wireup to perform pt2pt communications. 2013-10-04 02:58:26 +00:00
sensor As per the RFC, bring in the ORTE async progress code and the rewrite of OOB: 2013-08-22 16:37:40 +00:00
snapc As per the RFC, bring in the ORTE async progress code and the rewrite of OOB: 2013-08-22 16:37:40 +00:00
sstore Correctly register the component MCA parameters. 2013-06-15 16:05:09 +00:00
state As per the RFC, bring in the ORTE async progress code and the rewrite of OOB: 2013-08-22 16:37:40 +00:00