From ffd20e6c0a93e298b4bbed361ad91657577db821 Mon Sep 17 00:00:00 2001 From: David Ozog Date: Tue, 21 May 2024 12:51:40 -0400 Subject: [PATCH 1/2] Add some suggested doc-edits throughout the spec --- content/collective_intro.tex | 2 +- content/memmgmt_intro.tex | 2 +- content/teams_intro.tex | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/collective_intro.tex b/content/collective_intro.tex index a2752c613..a219422ba 100644 --- a/content/collective_intro.tex +++ b/content/collective_intro.tex @@ -19,7 +19,7 @@ \end{enumerate} Concurrent accesses to symmetric memory by an \openshmem collective -routine and any other means of access---where at least one updates the +routine and any other means of access---where at least one PE updates the symmetric memory---results in undefined behavior. Since \acp{PE} can enter and exit collectives at different times, accessing such memory remotely may require additional synchronization. diff --git a/content/memmgmt_intro.tex b/content/memmgmt_intro.tex index 393785ff5..8cb6605c0 100644 --- a/content/memmgmt_intro.tex +++ b/content/memmgmt_intro.tex @@ -3,7 +3,7 @@ symmetric data objects in the symmetric heap. The symmetric memory allocation routines differ from the private heap -allocation routines in that they must be called by all \acp{PE} in a +allocation routines in that they must be called by all \acp{PE} in the world team. When specified, each of these routines includes at least one call to a procedure that is semantically equivalent to \FUNC{shmem\_barrier\_all}. This ensures that all \acp{PE} diff --git a/content/teams_intro.tex b/content/teams_intro.tex index 851d1c1e0..cca6d01b7 100644 --- a/content/teams_intro.tex +++ b/content/teams_intro.tex @@ -21,7 +21,7 @@ \subsubsection*{Predefined and Application-Defined Teams} portion of an application. Any team successfully created by a \FUNC{shmem\_team\_split\_*} routine is valid until it is destroyed. -All valid teams have a least one member. +All valid teams have at least one member. \subsubsection*{Team Handles} @@ -84,7 +84,7 @@ \subsubsection*{Team Creation} \acp{PE} in a newly created team are consecutively numbered starting with \ac{PE} number 0. \acp{PE} are ordered by their \ac{PE} number in -the parent team. Team relative \ac{PE} +the parent team. Team-relative \ac{PE} numbers can be used for point-to-point operations through team-based contexts (see Section~\ref{sec:ctx}) or using the translation routine \FUNC{shmem\_team\_translate\_pe}. From 47e38ecf1048318eecdb9af8e908349444f98ccc Mon Sep 17 00:00:00 2001 From: David Ozog Date: Fri, 12 Jul 2024 16:10:27 -0400 Subject: [PATCH 2/2] Update content/collective_intro.tex --- content/collective_intro.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/collective_intro.tex b/content/collective_intro.tex index a219422ba..823164abe 100644 --- a/content/collective_intro.tex +++ b/content/collective_intro.tex @@ -19,7 +19,7 @@ \end{enumerate} Concurrent accesses to symmetric memory by an \openshmem collective -routine and any other means of access---where at least one PE updates the +routine and any other means of access---where at least one \ac{PE} updates the symmetric memory---results in undefined behavior. Since \acp{PE} can enter and exit collectives at different times, accessing such memory remotely may require additional synchronization.