From a471b533ecd5836930ad696c156b16ce8a1e3352 Mon Sep 17 00:00:00 2001 From: James Dinan Date: Fri, 31 Mar 2017 13:32:34 -0400 Subject: [PATCH] Revert "Merge pull request #38 from davidozog/pr/mem_manage_barriers" This reverts commit fc2c0162cde0151cf6d4d2edac351f6a887ab950, reversing changes made to 018862ff60b8c57ebddd6daa8d079419b06b5e26. --- content/shmem_malloc.tex | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/content/shmem_malloc.tex b/content/shmem_malloc.tex index 18697cb21..35e845bfd 100644 --- a/content/shmem_malloc.tex +++ b/content/shmem_malloc.tex @@ -43,16 +43,11 @@ \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\_align}, \FUNC{shmem\_free}, and \FUNC{shmem\_realloc} routines + The \FUNC{shmem\_malloc}, \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 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. - This ensures that all + \openshmem communication routines. Each of these routines call the + \FUNC{shmem\_barrier\_all} routine before returning; this ensures that all \ac{PE}s participate in the memory allocation, and that the memory on other \ac{PE}s can be used as soon as the local \ac{PE} returns. The user is responsible for calling these routines with identical argument(s) on all