1
1
openmpi/orte/mca
Ralph Castain 07f0a71faa Cleanup the show_help entries on the seq mapper
This commit was SVN r18191.
2008-04-17 14:43:15 +00:00
..
errmgr Bring some sanity to the exit code returned by mpirun. Ensure that we provide a non-zero code if something goes wrong, including someone exiting after calling mpi_init without calling mpi_finalize. 2008-03-19 19:00:51 +00:00
ess Add a binomial tree-based launch to ssh, turned "on" only when the plm_rsh_tree_spawned mca param is set to a non-zero value. This probably isn't a very optimized capability, but it does execute a tree-based launch that may scale better than linear at high node counts. 2008-04-14 18:26:08 +00:00
filem Bring some sanity to the exit code returned by mpirun. Ensure that we provide a non-zero code if something goes wrong, including someone exiting after calling mpi_init without calling mpi_finalize. 2008-03-19 19:00:51 +00:00
grpcomm Update the cnos module - should (hopefully) compile and work... 2008-04-09 22:33:00 +00:00
iof Remove the orte_proc_table. Migrate all users of it to the opal_hash_table and a new name hash function in orte. 2008-03-05 22:44:35 +00:00
odls Fix singleton and singleton comm_spawn 2008-04-16 14:38:10 +00:00
oob Always declare oob_tcp_disable_family, no matter if --disable-ipv6 is set. 2008-04-16 09:31:15 +00:00
plm Implement the seq rmaps module that sequentially maps process ranks to a list hosts in a hostfile. 2008-04-17 13:50:59 +00:00
ras Turn off the new fqdn behavior pending resolution of hostfile issue 2008-04-01 20:52:22 +00:00
rmaps Cleanup the show_help entries on the seq mapper 2008-04-17 14:43:15 +00:00
rml Cleanup and fix bugs in the MPI dynamics section. Modify the dpm API so it properly takes ports instead of process names (as correctly identified by Aurelien). Fix race conditions in the use of ompi-server. Fix incompatibilities between the mpi bindings and the dpm implemenation that could cause segfaults due to uninitialized memory. 2008-04-16 14:27:42 +00:00
routed Consolidate the daemon wireup message into the launch message. The daemons don't need their contact info prior to the launch message anyway. This not only eliminates a job-wide communication from the startup procedure, but it also resolves a race condition reported when operating across highly distributed (i.e., cross-country) networks. In such scenarios, it proved possible for a daemon to receive its launch message -before- it had received the contact info message, even though the latter had been sent first! 2008-04-10 15:35:11 +00:00
snapc For consistency reasons always use opal_home_directory and 2008-03-31 18:13:41 +00:00