From c5985a31b5dce93740f7e29e5a8552415399f3df Mon Sep 17 00:00:00 2001 From: James Dinan Date: Sun, 22 Mar 2020 18:57:35 -0400 Subject: [PATCH] Move context options to contexts intro Signed-off-by: James Dinan --- content/context_intro.tex | 29 ++++++++++++++++++++++++++++- content/shmem_ctx_create.tex | 28 ---------------------------- 2 files changed, 28 insertions(+), 29 deletions(-) diff --git a/content/context_intro.tex b/content/context_intro.tex index 552220c42..05d07a0f5 100644 --- a/content/context_intro.tex +++ b/content/context_intro.tex @@ -42,4 +42,31 @@ All point-to-point routines that operate on this context will do so with respect to the team-relative \ac{PE} numbering of the associated team. If the PE number passed to such a routine is invalid, being negative or greater -than or equal to the size of the \openshmem team, then the behavior is undefined. \ No newline at end of file +than or equal to the size of the \openshmem team, then the behavior is undefined. + +By default, contexts are {\em shareable} and, when it is allowed by the +threading model provided by the \openshmem library, they can be used concurrently by +multiple threads within the PE where they were created. +% +The following options can be supplied during context creation to restrict +this usage model and enable performance optimizations. When using a given +context, the application must comply with the requirements of all options +set on that context; otherwise, the behavior is undefined. +No options are enabled on the default context. + +\apitablerow{\LibConstRef{SHMEM\_CTX\_SERIALIZED}}{ + The given context is shareable; however, it will not be used by multiple threads + concurrently. When the \CONST{SHMEM\_CTX\_SERIALIZED} option is + set, the user must ensure that operations involving the given + context are serialized by the application.} + +\apitablerow{\LibConstRef{SHMEM\_CTX\_PRIVATE}}{ + The given context will be used only by the thread that created it.} + +\apitablerow{\LibConstRef{SHMEM\_CTX\_NOSTORE}}{ + Quiet and fence operations performed on the given context are not + required to enforce completion and ordering of memory store + operations. + When ordering of store operations is needed, the application must + perform a synchronization operation on a context without the + \CONST{SHMEM\_CTX\_NOSTORE} option enabled.} diff --git a/content/shmem_ctx_create.tex b/content/shmem_ctx_create.tex index 870baa4ce..dc6dde098 100644 --- a/content/shmem_ctx_create.tex +++ b/content/shmem_ctx_create.tex @@ -35,34 +35,6 @@ respect to the associated \ac{PE} team. That is, all point-to-point routines operating on this context will use team-relative \ac{PE} numbering. - - By default, contexts are {\em shareable} and, when it is allowed by the - threading model provided by the \openshmem library, they can be used concurrently by - multiple threads within the PE where they were created. - % - The following options can be supplied during context creation to restrict - this usage model and enable performance optimizations. When using a given - context, the application must comply with the requirements of all options - set on that context; otherwise, the behavior is undefined. - No options are enabled on the default context. - - \apitablerow{\LibConstRef{SHMEM\_CTX\_SERIALIZED}}{ - The given context is shareable; however, it will not be used by multiple threads - concurrently. When the \CONST{SHMEM\_CTX\_SERIALIZED} option is - set, the user must ensure that operations involving the given - context are serialized by the application.} - - \apitablerow{\LibConstRef{SHMEM\_CTX\_PRIVATE}}{ - The given context will be used only by the thread that created it.} - - \apitablerow{\LibConstRef{SHMEM\_CTX\_NOSTORE}}{ - Quiet and fence operations performed on the given context are not - required to enforce completion and ordering of memory store - operations. - When ordering of store operations is needed, the application must - perform a synchronization operation on a context without the - \CONST{SHMEM\_CTX\_NOSTORE} option enabled.} - } \apireturnvalues{