Для этого сайта требуется поддержка JavaScript.
Обзор
Помощь
Вход
ports
/
openmpi
Следить
1
В избранное
1
Форкнуть
0
Вы уже форкнули openmpi
Код
Релизы
Активность
openmpi
/
orte
/
mca
История
Ralph Castain
9a47e45a09
<laugh> ensure we really compare the things we want to compare
...
This commit was SVN r32055.
2014-06-19 20:54:25 +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
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
ess
Fix potential issue if opal_hwloc_topology is NULL
2014-06-19 18:52:41 +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
Cleanup: we were accidentally killing ourselves (bad idea)
2014-06-17 20:38:42 +00:00
oob
The TCP component will have set the hash table entry to NULL, but that doesn't remove the key. So the hash_table retrieval function will return success, but with a NULL pointer - protect against that scenario
2014-06-09 17:46:22 +00:00
plm
Mark the proc as alive so waitpid callback system doesn't immediately activate the callback
2014-06-18 14:04:55 +00:00
ras
Cleanup compile issues - missing updates to some plm components and the slurm ras component
2014-06-01 17:59:06 +00:00
rmaps
<laugh> ensure we really compare the things we want to compare
2014-06-19 20:54:25 +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
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
sstore
Mark the proc as alive so waitpid callback system doesn't immediately activate the callback
2014-06-18 14:04:55 +00:00
state
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