ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
70158790e5
openmpi/test/runtime
История
Greg Koenig 60485ff95f This is a very large change to rename several #define values from 
OMPI_* to OPAL_*.  This allows opal layer to be used more independent
from the whole of ompi.

NOTE: 9 "svn mv" operations immediately follow this commit.

This commit was SVN r21180.
2009-05-06 20:11:28 +00:00
..
Makefile.am Rename liborte to libopen-rte and libopal to libopen-pal per telecon today 2006-12-05 18:27:24 +00:00
opal_init_finalize.c * forgot to fix up includes in the test directory with yesterday's commit. 2006-02-12 19:51:24 +00:00
orte_init_finalize.c * forgot to fix up includes in the test directory with yesterday's commit. 2006-02-12 19:51:24 +00:00
README Merge in the new data support subsystem for ORTE. MPI folks should not notice a difference. Longer explanation will be sent to developers mailing list. 2006-02-07 03:32:36 +00:00
sigchld.c This is a very large change to rename several #define values from 2009-05-06 20:11:28 +00:00
start_shut.c These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC. 2007-10-05 19:48:23 +00:00

README 

The functions in this directory are all intended to test registry operations against a persistent seed. Thus, they perform a system init/finalize. The functions in the directory above this one should be used to test basic registry operations within the replica - they will isolate the replica so as to avoid the communications issues and the init/finalize problems in other subsystems that may cause problems here.

To run these tests, you need to first start a persistent daemon. This can be done using the command:

orted --seed --scope public --persistent

The daemon will "daemonize" itself and establish the registry (as well as other central services) replica, and then return a system prompt. You can then run any of these functions. If desired, you can utilize gdb and/or debug options on the persistent orted to watch/debug replica operations as well.