SHMEM_GET32(3)

πŸ“¦
version 5.0.10 Β· 4 versions
, in ubuntu stonking

✨ NAME ✨

okay bestie so πŸ’– this whole lil family of Open MPI calls β€” shmem_character_get(3), shmem_complex_get(3), shmem_double_get(3), shmem_float_get(3), shmem_get4(3), shmem_get8(3), shmem_get32(3), shmem_get64(3), shmem_get128(3), shmem_getmem(3), shmem_int_get(3), shmem_integer_get(3), shmem_logical_get(3), shmem_long_get(3), shmem_longdouble_get(3), shmem_longlong_get(3), shmem_real_get(3), and shmem_short_get(3) β€” all do the same iconic thing: they transfer data from a specified processing element (PE). periodt. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

C or C++

#include <mpp/shmem.h>

void shmem_get32(void *target, const void *source,
  size_t len, int pe)

void shmem_get64(void *target, const void *source,
  size_t len, int pe)

void shmem_get128(void *target, const void *source,
  size_t len, int pe)

void shmem_getmem(void *target, const void *source,
  size_t len, int pe)

void shmem_int_get(int *target, const int *source,
  size_t len, int pe)

void shmem_double_get(double *target, const double *source,
  size_t len, int pe)

void shmem_float_get(float *target, const float *source,
  size_t len, int pe)

void shmem_long_get(long *target, const long *source,
  size_t len, int pe)

void shmem_longdouble_get(long double *target,
  const long double *source, size_t len, int pe)

void shmem_longlong_get(long long *target,
  const long long *source, size_t len, int pe)

void shmem_short_get(short *target,
  const short *source, size_t len, int pe)

Fortran

INCLUDE "mpp/shmem.fh"

INTEGER len, pe

CALL SHMEM_CHARACTER_GET(target, source, len, pe)

CALL SHMEM_COMPLEX_GET(target, source, len, pe)

CALL SHMEM_DOUBLE_GET(target, source, len, pe)

CALL SHMEM_GET4(target, source, len, pe)

CALL SHMEM_GET8(target, source, len, pe)

CALL SHMEM_GET32(target, source, len, pe)

CALL SHMEM_GET64(target, source, len, pe)

CALL SHMEM_GET128(target, source, len, pe)

CALL SHMEM_GETMEM(target, source, len, pe)

CALL SHMEM_INTEGER_GET(target, source, len, pe)

CALL SHMEM_LOGICAL_GET(target, source, len, pe)

CALL SHMEM_REAL_GET(target, source, len, pe)

πŸ’« DESCRIPTION πŸ’«

so the shmem_get routines grab nelems elements of the data object sitting at address source on the remote PE pe, and drop them into the data object at address target on the local PE. and then β€” the part that matters β€” these routines return after the data has been copied to address target on the local PE. like, it's done by the time it comes back. no cap. πŸ’–

🫢 the arguments, bestie 🫢

  • target β€” the local data object getting updated. she's the one receiving. πŸ’β€β™€οΈ
  • source β€” the data object on the PE identified by pe that holds the data to be copied. this data object must be remotely accessible. like, important important.
  • len β€” number of elements in the target and source arrays. len must be of type integer. if you're in Fortran, it's gotta be a constant, variable, or array element of default integer type.
  • pe β€” the PE number of the remote PE. pe must be of type integer. if you're in Fortran, it must be a constant, variable, or array element of default integer type.

🌸 typing constraints (vibe check time) 🌸

the target and source data objects must conform to typing constraints, and here they are, one by one:

  • shmem_getmem β€” Fortran: any noncharacter type. C: any data type. len is scaled in bytes.
  • shmem_get4, shmem_get32 β€” any noncharacter type that has a storage size equal to 32 bits.
  • {shmem_get8, shmem_get64} β€” any noncharacter type that has a storage size equal to 64 bits.
  • shmem_get128 β€” any noncharacter type that has a storage size equal to 128 bits.
  • shmem_short_get β€” elements of type short.
  • shmem_int_get β€” elements of type int.
  • shmem_long_get β€” elements of type long.
  • shmem_longlong_get β€” elements of type long long.
  • shmem_float_get β€” elements of type float.
  • shmem_double_get β€” elements of type double.
  • shmem_longdouble_get β€” elements of type long double.
  • SHMEM_CHARACTER_GET β€” elements of type character. len is the number of characters to transfer. the actual character lengths of the source and target variables are ignored. not even looked at.
  • SHMEM_COMPLEX_GET β€” elements of type complex of default size.
  • SHMEM_DOUBLE_GET β€” (Fortran) elements of type double precision.
  • SHMEM_INTEGER_GET β€” elements of type integer.
  • SHMEM_LOGICAL_GET β€” elements of type logical.
  • SHMEM_REAL_GET β€” elements of type real.
πŸ’€ and if you're using Fortran, data types must be of default size. for example, a real variable must be declared as REAL, REAL*4, or REAL(KIND=4). don't be out here getting creative with kinds, she will not receive it.

πŸ“ NOTES πŸ“

see intro_shmem(3) for a definition of the term remotely accessible. iykyk, but if you don't, go read that one. πŸ¦‹


🌈 EXAMPLES 🌈

consider this simple example for Fortran, bestie:

PROGRAM REDUCTION
  REAL VALUES, SUM
  COMMON /C/ VALUES
  REAL WORK

  CALL START_PES(0) ! ALLOW ANY NUMBER OF PES
  VALUES = MY_PE() ! INITIALIZE IT TO SOMETHING
  CALL SHMEM_BARRIER_ALL
  SUM = 0.0
  DO I = 0,NUM_PES()-1
    CALL SHMEM_REAL_GET(WORK, VALUES, 1, I)
    SUM = SUM + WORK
  ENDDO
  PRINT *, 'PE ', MY_PE(), ' COMPUTED SUM=', SUM
  CALL SHMEM_BARRIER_ALL
END

see also πŸ‘€

intro_shmem(3) shmem_put(3) shmem_iget(3) shmem_quiet(3)


Copyright β€” 2003-2026, The Open MPI Community πŸ’œ

aaaand that's the whole page, babe πŸŽ€ this was the SHMEM_GET32(3) man page from Open MPI, last touched Sep 10, 2026, and honestly? iconic. go forth and transfer your data, you've got this. 🫢✨

πŸ“¦ where this page comes from