mpid_win.tex

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

\startmanpage
\mantitle{MPID{\tt \char`\_}Win}{tex}{10/7/2002}
\manname{MPID{\tt \char`\_}Win}
--- Description of the Window Object data structure. 
\subhead{Synopsis}
\startvb\begin{verbatim}
typedef struct {
    int          handle;         /* value of MPI_Win for this structure */
    volatile int ref_count;
    void         *start_address; /* Address and length of *local* window */
    MPI_Aint     length;        
    int          disp_unit;      /* Displacement unit of *local* window */
    MPID_List    attributes;
    MPID_Comm    *comm;         /* communicator of window */
    char         name[MPI_MAX_OBJECT_NAME];  
    MPID_Errhandler *errhandler;  /* Pointer to the error handler structure */
    /* other, device-specific information 
       This is likely to include a list of pending RMA operations
       (i.e., MPI_Put, MPI_Get, and MPI_Accumulate)
     */
} MPID_Win;

\end{verbatim}
\endvb

\subhead{Module}
Win-DS
\par
\subhead{Notes}
The following 3 keyvals are defined for attributes on all MPI
Window objects:
\begin{verbatim}
 MPI_WIN_SIZE
 MPI_WIN_BASE
 MPI_WIN_DISP_UNIT
\end{verbatim}

These correspond to the values in {\tt length}, {\tt start{\tt \char`\_}address}, and
{\tt disp{\tt \char`\_}unit}.
\par
The communicator in the window is the same communicator that the user
provided to {\tt MPI{\tt \char`\_}Win{\tt \char`\_}create} (not a dup).  However, each intracommunicator
has a special context id that may be used if MPI communication is used
by the implementation to implement the RMA operations.
\par
There is no separate window group; the group of the communicator should be
used.
\par
\subhead{Question}
Should a {\tt MPID{\tt \char`\_}Win} be defined after {\tt MPID{\tt \char`\_}Segment} in case the device
wants to
store a queue of pending put/get operations, described with {\tt MPID{\tt \char`\_}Segment
}(or {\tt MPID{\tt \char`\_}Request})s?
\par
\endmanpage