Skip to content

Commit

Permalink
Give align the same barrier requirement as malloc
Browse files Browse the repository at this point in the history
Adds a barrier at exit requirement to shmem_align (same as
shmem_malloc).  Also, change explicit requirement for a call to
shmem_barrier_all to the less restrictive "semantic equivalence".

Signed-off-by: David Ozog <[email protected]>
  • Loading branch information
davidozog committed Mar 8, 2017
1 parent fd48bbe commit bf356e5
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions content/shmem_malloc.tex
Original file line number Diff line number Diff line change
Expand Up @@ -43,11 +43,12 @@
\CONST{NULL} pointer, the block to which it points is freed. If the space cannot
be allocated, the block to which \VAR{ptr} points is unchanged.

The \FUNC{shmem\_malloc}, \FUNC{shmem\_free}, and \FUNC{shmem\_realloc} routines
The \FUNC{shmem\_malloc}, \FUNC{shmem\_align}, \FUNC{shmem\_free}, and \FUNC{shmem\_realloc} routines
are provided so that multiple \ac{PE}s in a program can allocate symmetric,
remotely accessible memory blocks. These memory blocks can then be used with
\openshmem communication routines. Each of these routines include at least one
call to \FUNC{shmem\_barrier\_all}: \FUNC{shmem\_malloc} calls a
call to a procedure that is semantically equivalent to \FUNC{shmem\_barrier\_all}:
\FUNC{shmem\_malloc} and \FUNC{shmem\_align} call a
barrier on exit; \FUNC{shmem\_free} calls a barrier on entry; and
\FUNC{shmem\_realloc} may call barriers on both entry and exit, depending on
whether an existing allocation is modified and whether new memory is allocated.
Expand Down

0 comments on commit bf356e5

Please sign in to comment.