openmpi/ompi/tools/ompi-profiler/ompi-profiler.1in

.\"
.\" Copyright (c) 2007 Los Alamos National Security, LLC
.\"                    All rights reserved.
.\" Copyright (c) 2008 Sun Microsystems, Inc.  All rights reserved.
.\"
.\" Man page for OMPI's ompi-server command
.\" 
.\" .TH name     section center-footer   left-footer  center-header
.TH     OMPI-SERVER  1 "#OMPI_DATE#" "#PACKAGE_VERSION#" "#PACKAGE_NAME#"
.\" **************************
.\"    Name Section
.\" **************************
.SH NAME
.
ompi-server \- Server for supporting name publish/lookup operations.
.
.PP
.
.\" **************************
.\"    Synopsis Section
.\" **************************
.SH SYNOPSIS
.
.BR ompi-server " [ options ]"
.
.\" **************************
.\"    Options Section
.\" **************************
.SH Options
.
\fIompi-server\fR acts as a data server for Open MPI jobs to exchange
contact information in support of MPI-2's Publish_name and Lookup_name
functions.
.
.TP 10
.B -h | --help
Display help for this command
.
.
.TP
.B -d | --debug
Enable verbose output for debugging
.
.
.TP
.B -r | --report-uri \fR<value>\fP
Report the Open MPI contact information for the server. This information is
required for MPI jobs to use the data server. Three parameter values are supported:
(a) '-', indicating that the uri is to be printed to stdout; (b) '+', indicating that
the uri is to be printed to stderr; and (c) "file:path-to-file", indicating that
the uri is to be printed to the specified file. The "path-to-file" can be either
absolute or relative, but must be in a location where the user has write
permissions. Please note that the resulting file must be read-accessible to
expected users of the server.
.
.
.\" **************************
.\"    Description Section
.\" **************************
.SH DESCRIPTION
.
.PP
\fIompi-server\fR acts as a data server for Open MPI jobs to exchange
contact information in support of MPI-2's Publish_name and Lookup_name
functions.
.
.\" **************************
.\"    See Also Section
.\" **************************
.
.SH SEE ALSO
.
Enable modex-less launch. Consists of: 1. minor modification to include two new opal MCA params: (a) opal_profile: outputs what components were selected by each framework currently enabled for most, but not all, frameworks (b) opal_profile_file: name of file that contains profile info required for modex 2. introduction of two new tools: (a) ompi-probe: MPI process that simply calls MPI_Init/Finalize with opal_profile set. Also reports back the rml IP address for all interfaces on the node (b) ompi-profiler: uses ompi-probe to create the profile_file, also reports out a summary of what framework components are actually being used to help with configuration options 3. modification of the grpcomm basic component to utilize the profile file in place of the modex where possible 4. modification of orterun so it properly sees opal mca params and handles opal_profile correctly to ensure we don't get its profile 5. similar mod to orted as for orterun 6. addition of new test that calls orte_init followed by calls to grpcomm.barrier This is all completely benign unless actively selected. At the moment, it only supports modex-less launch for openib-based systems. Minor mod to the TCP btl would be required to enable it as well, if people are interested. Similarly, anyone interested in enabling other BTL's for modex-less operation should let me know and I'll give you the magic details. This seems to significantly improve scalability provided the file can be locally located on the nodes. I'm looking at an alternative means of disseminating the info (perhaps in launch message) as an option for removing that constraint. This commit was SVN r20098. 2008-12-10 02:49:02 +03:00			`.\"`
			`.\" Copyright (c) 2007 Los Alamos National Security, LLC`
			`.\" All rights reserved.`
			`.\" Copyright (c) 2008 Sun Microsystems, Inc. All rights reserved.`
			`.\"`
			`.\" Man page for OMPI's ompi-server command`
			`.\"`
			`.\" .TH name section center-footer left-footer center-header`
			`.TH OMPI-SERVER 1 "#OMPI_DATE#" "#PACKAGE_VERSION#" "#PACKAGE_NAME#"`
			`.\" **************************`
			`.\" Name Section`
			`.\" **************************`
			`.SH NAME`
			`.`
			`ompi-server \- Server for supporting name publish/lookup operations.`
			`.`
			`.PP`
			`.`
			`.\" **************************`
			`.\" Synopsis Section`
			`.\" **************************`
			`.SH SYNOPSIS`
			`.`
			`.BR ompi-server " [ options ]"`
			`.`
			`.\" **************************`
			`.\" Options Section`
			`.\" **************************`
			`.SH Options`
			`.`
			`\fIompi-server\fR acts as a data server for Open MPI jobs to exchange`
			`contact information in support of MPI-2's Publish_name and Lookup_name`
			`functions.`
			`.`
			`.TP 10`
			`.B -h \| --help`
			`Display help for this command`
			`.`
			`.`
			`.TP`
			`.B -d \| --debug`
			`Enable verbose output for debugging`
			`.`
			`.`
			`.TP`
			`.B -r \| --report-uri \fR<value>\fP`
			`Report the Open MPI contact information for the server. This information is`
			`required for MPI jobs to use the data server. Three parameter values are supported:`
			`(a) '-', indicating that the uri is to be printed to stdout; (b) '+', indicating that`
			`the uri is to be printed to stderr; and (c) "file:path-to-file", indicating that`
			`the uri is to be printed to the specified file. The "path-to-file" can be either`
			`absolute or relative, but must be in a location where the user has write`
			`permissions. Please note that the resulting file must be read-accessible to`
			`expected users of the server.`
			`.`
			`.`
			`.\" **************************`
			`.\" Description Section`
			`.\" **************************`
			`.SH DESCRIPTION`
			`.`
			`.PP`
			`\fIompi-server\fR acts as a data server for Open MPI jobs to exchange`
			`contact information in support of MPI-2's Publish_name and Lookup_name`
			`functions.`
			`.`
			`.\" **************************`
			`.\" See Also Section`
			`.\" **************************`
			`.`
			`.SH SEE ALSO`
			`.`