GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  MPIX_T_PVAR_GET_INFO (3)

NAME

MPIX_T_pvar_get_info - XXX description here

CONTENTS

Synopsis
Input/output Parameters
Input Parameters
Output Parameters
Thread And Interrupt Safety
Notes For Fortran
Errors
Location

SYNOPSIS

int MPIX_T_pvar_get_info(int pvar_index, char *name, int *name_len, int *verbosity, int *var_class, MPI_Datatype *datatype, MPIX_T_enum *enumtype, char *desc, int *desc_len, int *binding, int *readonly, int *continuous, int *atomic)

INPUT/OUTPUT PARAMETERS

name_len
  - length of the string and/or buffer for name (integer)
desc_len
  - length of the string and/or buffer for desc (integer)

INPUT PARAMETERS

pvar_index
  - index of the performance variable to be queried between 0 and num_pvar-1 (integer)

OUTPUT PARAMETERS

name - buffer to return the string containing the name of the performance variable (string)
verbosity
  - verbosity level of this variable (integer)
var_class
  - class of performance variable (integer)
datatype
  - MPI type of the information stored in the performance variable (handle)
enumtype
  - optional descriptor for enumeration information (handle)
desc - buffer to return the string containing a description of the performance variable (string)
binding
  - type of MPI object to which this variable must be bound (integer)
readonly
  - flag indicating whether the variable can be written/reset (integer)
continuous
  - flag indicating whether the variable can be started and stopped or is continuously active (integer)
atomic
  - flag indicating whether the variable can be atomically read and reset (integer)

THREAD AND INTERRUPT SAFETY

This routine is thread-safe. This means that this routine may be safely used by multiple threads without the need for any user-provided thread locks. However, the routine is not interrupt safe. Typically, this is due to the use of memory allocation routines such as malloc or other non-MPICH runtime routines that are themselves not interrupt-safe.

NOTES FOR FORTRAN

All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have an additional argument ierr at the end of the argument list. ierr is an integer and has the same meaning as the return value of the routine in C. In Fortran, MPI routines are subroutines, and are invoked with the call statement.

All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in Fortran.

ERRORS

All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error value; C routines as the value of the function and Fortran routines in the last argument. Before the value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job. The error handler may be changed with MPI_Comm_set_errhandler (for communicators), MPI_File_set_errhandler (for files), and MPI_Win_set_errhandler (for RMA windows). The MPI-1 routine MPI_Errhandler_set may be used but its use is deprecated. The predefined error handler MPI_ERRORS_RETURN may be used to cause error values to be returned. Note that MPI does not guarentee that an MPI program can continue past an error; however, MPI implementations will attempt to continue whenever possible.

LOCATION

src/mpi_t/pvar_get_info.c
Search for    or go to Top of page |  Section 3 |  Main Index


MPIX_T_PVAR_GET_INFO (3) 9/20/2012

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.