1
1
openmpi/orte/mca
2014-09-10 17:36:16 +00:00
..
dfs Per the PMIx RFC: 2014-08-21 18:56:47 +00:00
errmgr Resolve a race condition that could cause us to hang during abnormal terminations due to multi-counting num_terminated 2014-09-02 00:32:52 +00:00
ess Re-enable the usock oob component. Ensure the TCP component promotes messages for other procs to the OOB base so that other components have a chance to send the relay. Seems to be passing MTT, so let's see how it works for others. 2014-08-30 19:33:46 +00:00
filem Per the PMIx RFC: 2014-08-21 18:56:47 +00:00
grpcomm Avoid conflicts when multiple collectives are underway in ORTE by giving each grpcomm component its own RML tag and posting persistent receives. We use the signature anyway to determine which collective the received message is addressing, so there is no need to post non-persistent receives. 2014-09-10 17:36:16 +00:00
iof Per the PMIx RFC: 2014-08-21 18:56:47 +00:00
odls Resolve a race condition that could cause us to hang during abnormal terminations due to multi-counting num_terminated 2014-09-02 00:32:52 +00:00
oob Properly protect the MCA parameters being registered by the OOB/TCP component when IPv6 is enabled 2014-09-02 14:53:00 +00:00
plm Since we've run into the situation where someone puts a script wrapper around a launcher such as srun, we need to always protect MCA cmd line params with quotes. This means we also need to protect the backend from quotes coming into the system as part of a value, or else the parser gets confused. 2014-09-08 20:38:46 +00:00
ras Some minor uninitialized variable cleanups 2014-08-29 02:21:13 +00:00
rmaps Per patch from Tetsuya, allow the user to bind-to none when specifying multiple pe's/rank as requested by Reuti. This allows the user to reserve multiple "slots" in the allocation for each process while mapping, but not to bind the process to specific processing elements on the node. 2014-09-10 15:52:18 +00:00
rml Avoid conflicts when multiple collectives are underway in ORTE by giving each grpcomm component its own RML tag and posting persistent receives. We use the signature anyway to determine which collective the received message is addressing, so there is no need to post non-persistent receives. 2014-09-10 17:36:16 +00:00
routed Per the PMIx RFC: 2014-08-21 18:56:47 +00:00
rtc check-help-strings cleanup 2014-08-11 03:26:21 +00:00
snapc Per the PMIx RFC: 2014-08-21 18:56:47 +00:00
sstore use the orte attributes in the FT code to fix compile errors 2014-06-26 03:19:17 +00:00
state Fix a race condition caused by a bad attribute flag that created an OR instead of an AND condition check 2014-08-22 22:48:16 +00:00