Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per PE Quiet interface #316

Merged
merged 9 commits into from
Jul 1, 2022
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions content/shmem_pe_quiet.tex
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
\apisummary{
Waits for completion of all outstanding memory store, blocking
\PUT{}, \ac{AMO}, and \emph{put-with-signal}, as well as
nonblocking \PUT{}, \emph{put-with-signal}, and \GET{} routines
to symmetric data objects issued by the calling \ac{PE} at the target
\acp{PE}.
}

\begin{apidefinition}

\begin{Csynopsis}
void @\FuncDecl{shmem\_pe\_quiet}@(const int *target_pes, size_t npes);
void @\FuncDecl{shmem\_ctx\_pe\_quiet}@(shmem_ctx_t ctx, const int *target_pes, size_t
npes);
manjugv marked this conversation as resolved.
Show resolved Hide resolved
\end{Csynopsis}

\begin{apiarguments}
\apiargument{IN}{ctx}{A context handle specifying the context on which to perform the operation.
When this argument is not provided, the operation is performed on
the default context.}
\apiargument{IN}{target\_pes}{Address of target \ac{PE} array where the
operations need to be completed}
\apiargument{IN}{npes}{The number of \acp{PE} in the target \ac{PE} array}

\end{apiarguments}

\apidescription{
The \FUNC{shmem\_pe\_quiet} ensures completion of memory store, blocking
\PUT{}, \ac{AMO}, and \emph{put-with-signal}, as well as nonblocking
\PUT{}, \emph{put-with-signal}, and \GET{} routines on the symmetric data
objects issued by the calling \ac{PE} to the target \acp{PE} and on the
given context.

The completion and visibility semantics of these operations are the same as the
\FUNC{shmem\_quiet} routine. However, it applies only to the target
\acp{PE}, i.e., the routines to the target \acp{PE} are guaranteed to be
manjugv marked this conversation as resolved.
Show resolved Hide resolved
complete and visible to all \acp{PE} when \FUNC{shmem\_pe\_quiet} returns.
When calling with the \FUNC{shmem\_ctx\_pe\_quiet} interface, the updates are
guaranteed to be complete and visible only to the \acp{PE} in the team used to
create the context.
manjugv marked this conversation as resolved.
Show resolved Hide resolved
}
\apireturnvalues{
None.
}

\apinotes{
manjugv marked this conversation as resolved.
Show resolved Hide resolved
On certain platforms, when \FUNC{shmem\_pe\_quiet} is invoked on a set of \acp{PE},
the performance might be equivalent to \FUNC{shmem\_quiet}.
}
\end{apidefinition}
manjugv marked this conversation as resolved.
Show resolved Hide resolved
3 changes: 3 additions & 0 deletions main_spec.tex
Original file line number Diff line number Diff line change
Expand Up @@ -473,6 +473,9 @@ \subsubsection{\textbf{SHMEM\_FENCE}}\label{subsec:shmem_fence}
\subsubsection{\textbf{SHMEM\_QUIET}}\label{subsec:shmem_quiet}
\input{content/shmem_quiet.tex}

\subsubsection{\textbf{SHMEM\_PE\_QUIET}}\label{subsec:shmem_quiet}
\input{content/shmem_pe_quiet.tex}

\subsubsection{Synchronization and Communication Ordering in OpenSHMEM}
\input{content/synchronization_model.tex}

Expand Down