mpid_request.tex

来自「刚才是说明 现在是安装程序在 LINUX环境下进行编程的MPICH安装文件」· TEX 代码 · 共 41 行

\startmanpage
\mantitle{MPID{\tt \char`\_}Request}{tex}{10/7/2002}
\manname{MPID{\tt \char`\_}Request}
--- Description of the Request data structure 
\subhead{Synopsis}
\startvb\begin{verbatim}
typedef struct {
    int          handle;  /* Value of MPI_Request for this structure */
    volatile int ref_count;
    MPID_Request_kind kind; /* Kind of request */
    /* The various types of requests may define subclasses for each 
       kind.  In particular, the user and persistent requests need
       special information */
    volatile int cc;      /* Completion counter */
    int volatile *cc_ptr;
    /* Pointer to the completion counter associated with a group of requests.
       When the counter reaches zero, the group of requests is complete. */
    MPI_Status status;
    MPID_Segment segment;
    MPID_Comm    *comm;   /* Originating Comm; needed to find error
                             handler if necessary */
    /* other, device-specific information */
} MPID_Request;

\end{verbatim}
\endvb

\subhead{Module}
Request-DS
\par
\subhead{Notes}
If it is necessary to remember the MPI datatype, this information is
saved within the {\tt segment}, not as part of a separate {\tt MPID{\tt \char`\_}Datatype
}entry.
\par
Requests come in many flavors, as stored in the {\tt kind} field.  It is
expected that each kind of request will have its own structure type
(e.g., {\tt MPID{\tt \char`\_}Request{\tt \char`\_}send{\tt \char`\_}t}) that extends the {\tt MPID{\tt \char`\_}Request}.
\par
\endmanpage