SHMEM_IGET128(3)

📦
version 5.0.10 · 4 versions
, in ubuntu stonking

👑 NAME 👑

hey bestie, welcome to the Open MPI manual for shmem_iget128(3) ✨ — one page, but it's a whole girlband, fr fr. Here's the entire lineup of strided get routines, all here to transfers strided data from a specified processing element (PE) 🌈:

✨ SYNOPSIS ✨

C or C++:

#include <mpp/shmem.h>

void shmem_iget32(void *target, const void *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_iget64(void *target, const void *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_iget128(void *target, const void *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_int_iget(int *target, const int *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_double_iget(double *target, const double *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_float_iget(float *target, const float *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_long_iget(long *target, const long *source,
  ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_longdouble_iget(long double *target,
  const long double *source, ptrdiff_t tst, ptrdiff_t sst,size_t len, int pe)

void shmem_longlong_iget(long long *target,
  const long long *source, ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

void shmem_short_iget(short *target,
  const short *source, ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)

Fortran:

INCLUDE "mpp/shmem.fh"

INTEGER tst, sst, len, pe

CALL SHMEM_COMPLEX_IGET(target, source, tst, sst, len,
& pe)

CALL SHMEM_DOUBLE_IGET(target, source, tst, sst, len,
& pe)

CALL SHMEM_IGET4(target, source, tst, sst, len, pe)

CALL SHMEM_IGET8(target, source, tst, sst, len, pe)

CALL SHMEM_IGET32(target, source, tst, sst, len, pe)

CALL SHMEM_IGET64(target, source, tst, sst, len, pe)

CALL SHMEM_IGET128(target, source, tst, sst, len, pe)

CALL SHMEM_INTEGER_IGET(target, source, tst, sst, len,
& pe)

CALL SHMEM_LOGICAL_IGET(target, source, tst, sst, len,
& pe)

CALL SHMEM_REAL_IGET(target, source, tst, sst, len, pe)

💖 DESCRIPTION 💖

okay so the strided get routines pull array data that lives at address source on a remote PE (pe) 🫶. The elements of the source array are spaced out by a stride called sst, and once that data lands, it gets stashed at the local memory address target, spaced out by stride tst. And here's the moment you've been waiting for bestie: the routines return when the data has been copied into the local target array. 👑

🎀 The arguments 🎀

  • target — the array that gets updated on the local PE. periodt.
  • source — the array holding the data to be copied, over on the remote PE.
  • tst — the stride between consecutive elements of the target array. It gets scaled by the element size of the target array. A value of 1 means contiguous data (no gaps, clean, slay). tst must be of type integer. If you're calling from Fortran, it must be a default integer value.
  • sst — the stride between consecutive elements of the source array. Also scaled by the element size of the array it's describing (the source one). A value of 1 means contiguous data. sst must be of type integer. If you're calling from Fortran, it must be a default integer value.
  • len — number of elements in the target and source arrays. len must be of type integer. If you're 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're using Fortran, it must be a constant, variable, or array element of default integer type.

🦋 Typing constraints 🦋

the target and source data objects have to conform to typing constraints, and here they are, no cap:

  • shmem_iget32, shmem_iget4: any noncharacter type that has a storage size equal to 32 bits.
  • shmem_iget64, shmem_iget8: any noncharacter type that has a storage size equal to 64 bits.
  • shmem_iget128: any noncharacter type that has a storage size equal to 128 bits.
  • shmem_short_iget: elements of type short.
  • shmem_int_iget: elements of type int.
  • shmem_long_iget: elements of type long.
  • shmem_longlong_iget: elements of type long long.
  • shmem_float_iget: elements of type float.
  • shmem_double_iget: elements of type double.
  • shmem_longdouble_iget: elements of type long double.
  • SHMEM_COMPLEX_IGET: elements of type complex of default size.
  • SHMEM_DOUBLE_IGET: (Fortran) elements of type double precision.
  • SHMEM_INTEGER_IGET: elements of type integer.
  • SHMEM_LOGICAL_IGET: elements of type logical.
  • SHMEM_REAL_IGET: elements of type real.
💀 okay so the source page literally lists these last five again, a second time, back to back: shmem_longdouble_iget — elements of type long double; SHMEM_COMPLEX_IGET — elements of type complex of default size; SHMEM_DOUBLE_IGET — (Fortran) elements of type double precision; SHMEM_INTEGER_IGET — elements of type integer; SHMEM_LOGICAL_IGET — elements of type logical; SHMEM_REAL_IGET — elements of type real. We're keeping it because the rule is keep everything, but yeah. It's giving déjà vu 💅

And one more thing: 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).

🌸 NOTES 🌸

hit up intro_shmem(3) for a definition of the term remotely accessible — iykyk 🧚

🔥 EXAMPLES 🔥

here's a lil Fortran moment using shmem_logical_iget ✨. Compile this one with the -lsma compiler option, bestie:

PROGRAM STRIDELOGICAL
  LOGICAL SOURCE(10), TARGET(5)
  SAVE SOURCE ! SAVE MAKES IT REMOTELY ACCESSIBLE
  DATA SOURCE /.T.,.F.,.T.,.F.,.T.,.F.,.T.,.F.,.T.,.F./
  DATA TARGET / 5*.F. /

  CALL START_PES(2)
  IF (MY_PE() .EQ. 0) THEN
    CALL SHMEM_LOGICAL_IGET(TARGET, SOURCE, 1, 2, 5, 1)
    PRINT*,'TARGET AFTER SHMEM_LOGICAL_IGET:',TARGET
  ENDIF
  CALL SHMEM_BARRIER_ALL
END

🌈 SEE ALSO 🌈

intro_shmem(3) shmem_get(3) shmem_quiet(3) — go read those next, you got this 🫶

Copyright 2003-2026, The Open MPI Community 🎀

and that's the whole page bestie 💖 this was the Open MPI SHMEM_IGET128(3) manual page, dated Sep 10, 2026, and the footer was literally just the name and that date again, so. iconic. bye now 🦋✨

📦 where this page comes from