Skip to content

Latest commit

 

History

History
82 lines (57 loc) · 2.12 KB

MPI_Grequest_complete.3.rst

File metadata and controls

82 lines (57 loc) · 2.12 KB
Raw

MPI_Grequest_complete

:ref:`MPI_Grequest_complete` |mdash| Reports that a generalized request is complete.

SYNTAX

C Syntax

#include <mpi.h>

int MPI_Grequest_complete(MPI_Request request)

Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'

MPI_GREQUEST_COMPLETE(REQUEST, IERROR)
    INTEGER REQUEST, IERROR

Fortran 2008 Syntax

USE mpi_f08

MPI_Grequest_complete(request, ierror)
    TYPE(MPI_Request), INTENT(IN) :: request
    INTEGER, OPTIONAL, INTENT(OUT) :: ierror

INPUT/OUTPUT PARAMETER

  • request : Generalized request (handle).

OUTPUT PARAMETER

  • ierror : Fortran only: Error status (integer).

DESCRIPTION

:ref:`MPI_Grequest_complete` informs MPI that the operations represented by the generalized request request are complete. A call to MPI_Wait(request, status)`` will return, and a call to MPI_Test(request, flag, status)`` will return flag=true only after a call to :ref:`MPI_Grequest_complete` has declared that these operations are complete.

MPI imposes no restrictions on the code executed by the callback functions. However, new nonblocking operations should be defined so that the general semantic rules about MPI calls such as :ref:`MPI_Test`, :ref:`MPI_Request_free`, or :ref:`MPI_Cancel` still hold. For example, all these calls are supposed to be local and nonblocking. Therefore, the callback functions query_fn, free_fn, or cancel_fn should invoke blocking MPI communication calls only if the context is such that these calls are guaranteed to return in finite time. Once :ref:`MPI_Cancel` has been invoked, the canceled operation should complete in finite time, regardless of the state of other processes (the operation has acquired "local" semantics). It should either succeed or fail without side-effects. The user should guarantee these same properties for newly defined operations.

ERRORS