Scroll to navigation

MPI_SESSION_GET_PSET_INFO(3) Open MPI MPI_SESSION_GET_PSET_INFO(3)

MPI_Session_get_pset_info — Returns an info object containing properties of a specific process set

SYNTAX

C Syntax

#include <mpi.h>
int MPI_Session_get_pset_info(MPI_Session session, const char *pset_name, MPI_Info *info)


Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_SESSION_GET_PSET_INFO(SESSION, PSET_NAME, INFO, IERROR)


    INTEGER SESSION, INFO, IERROR


    CHARACTER*(*) PSET_NAME


Fortran 2008 Syntax

USE mpi_f08
MPI_Session_get_pset_info(session, pset_name, info, ierror)


    TYPE(MPI_Session), INTENT(IN) :: session


    CHARACTER(LEN=*), INTENT(IN) :: pset_name


    TYPE(MPI_Info), INTENT(OUT) :: info


    INTEGER, OPTIONAL, INTENT(OUT) :: ierror


INPUT PARAMETERS

  • session : session (handle)
  • pset_name : name of process set (string)

OUTPUT PARAMETERS

  • info : info object (handle)
  • ierror : Fortran only: Error status (integer).

DESCRIPTION

MPI_Session_get_pset_info is used to query properties of a specific process set. The returned info object can be queried with existing MPI info object query functions. One key/value pair must be defined, “mpi_size”. The value of the “mpi_size” key specifies the number of MPI processes in the process set.

NOTES

The user is responsible for freeing the returned info object via MPI_Info_free.

ERRORS

Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.

Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions.

Open MPI includes three predefined error handlers that can be used:

  • MPI_ERRORS_ARE_FATAL Causes the program to abort all connected MPI processes.
  • MPI_ERRORS_ABORT An error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process.
  • MPI_ERRORS_RETURN Returns an error code to the application.

MPI applications can also implement their own error handlers by calling:

  • MPI_Comm_create_errhandler then MPI_Comm_set_errhandler
  • MPI_File_create_errhandler then MPI_File_set_errhandler
  • MPI_Session_create_errhandler then MPI_Session_set_errhandler or at MPI_Session_init
  • MPI_Win_create_errhandler then MPI_Win_set_errhandler

Note that MPI does not guarantee that an MPI program can continue past an error.

See the MPI man page for a full list of MPI error codes.

See the Error Handling section of the MPI-3.1 standard for more information.

SEE ALSO:

MPI_Session_init


COPYRIGHT

2003-2024, The Open MPI Community

December 2, 2024