SHMEM_GET128(3)

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

πŸ’– SHMEM_GET128(3) πŸ’– Open MPI edition 🌈

okay so bestie, welcome to the shmem_get cinematic universe β€” this is the manpage for the whole get squad, and yes, they're all serving the exact same iconic energy with slightly different types. 🫢


🌸 NAME 🌸

The whole squad, in order, no one left behind:

…and the job description for every single one of them? Transfers data from a specified processing element (PE). that's the whole personality. 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 here's the tea β˜• β€” the shmem_get routines transfer nelems elements of the data object at address source on the remote PE pe, over to the data object at address target on the local PE. They only come back once the data has actually been copied to address target on the local PE. no half-finished vibes here, the function returns when it's done done. πŸ’…

πŸŽ€ The arguments, explained with love

  • target β€” Local data object to be updated. this is the glow-up destination, bestie.
  • source β€” Data object on the PE identified by pe that contains the data to be copied. this data object must be remotely accessible. non-negotiable.
  • len β€” Number of elements in the target and source arrays. len must be of type integer. If you are using Fortran, it must be a constant, variable, or array element of default integer type.
  • pe β€” PE number of the remote PE. pe must be of type integer. If you are using Fortran, it must be a constant, variable, or array element of default integer type.

🌈 Typing constraints (aka who's allowed to hang out with whom) πŸ‘‘

The target and source data objects must conform to the following typing constraints, fr fr:

  • 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.
  • 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.
🚨 Fortran besties listen up: if you are 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 get cute with it unless you want sadness. 😭

πŸ“ 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 β€” it's giving main character energy, honestly:

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

look at them go. pulling WORK from every PE one at a time and summing it up. absolute queens. πŸ‘‘

πŸ‘€ See also


2003-2026, The Open MPI Community


πŸ’– and that's the whole page bestie!! this one's from the Open MPI crew, copyrighted 2003-2026, The Open MPI Community, dated Sep 10, 2026. go forth and get your data, you gorgeous distributed-systems icon. slay. πŸ’…βœ¨πŸ¦‹πŸŒΈ
πŸ“¦ where this page comes from