SHMEM_LONGLONG_IPUT(3)

📦
version 5.0.10 · 4 versions
, in ubuntu stonking

hiii bestie 💖 pull up a chair, we're reading the SHMEM_LONGLONG_IPUT(3) page from the Open MPI manual together. no cap, it's lowkey a banger. it's giving "strided data transfer" and honestly? obsessed. 💅

✨ NAME ✨

okay so this page is a whole family reunion 🫶 — every single one of these routines does the exact same strided-put thing, they just show up dressed for a different element type. the full guest list:

and what do they all do? Transfer strided data to a specified processing element (PE). that's it, that's the whole vibe. periodt. 💖

🌸 SYNOPSIS 🌸

C or C++

#include <mpp/shmem.h>

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

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

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

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

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

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

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

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

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

void shmem_short_iput(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_IPUT(target, source, tst, sst, len,
& pe)

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

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

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

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

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

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

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

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

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

🦋 DESCRIPTION 🦋

so here's the tea, bestie ☕: the shmem_iput routines read the elements of a local array (source) and write them to a remote array (target) on the PE you point at with pe. and the timing? these routines return once the data has been copied out of the source array on the local PE — but not necessarily before the data has actually been delivered to the remote data object. so like, the local side is done, the remote side is still doing its thang. don't @ me. 😭

the arguments are as follows:

  • target — The array to be updated on the remote PE. this data object must be remotely accessible. no exceptions, she's picky. ✨
  • source — The array containing the data to be copied.
  • tst — The stride between consecutive elements of the target array. the stride is scaled by the element size of the target array. a value of 1 indicates contiguous data. tst must be of type integer. if you're in Fortran, it must be a default integer value.
  • sst — The stride between consecutive elements of the source array. the stride is scaled by the element size of the source array. a value of 1 indicates contiguous data. sst must be of type integer. if you're in 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 in 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 in Fortran, it must be a constant, variable, or array element of default integer type.

the target and source data objects must conform to typing constraints, which are, in no particular order of slay:

  • shmem_iput32, shmem_iput4: Any noncharacter type that has a storage size equal to 32 bits.
  • shmem_iput64, shmem_iput8: Any noncharacter type that has a storage size equal to 64 bits.
  • shmem_iput128: Any noncharacter type that has a storage size equal to 128 bits.
  • shmem_short_iput: Elements of type short.
  • shmem_int_iput: Elements of type int.
  • shmem_long_iput: Elements of type long.
  • shmem_longlong_iput: Elements of type long long.
  • shmem_float_iput: Elements of type float.
  • shmem_double_iput: Elements of type double.
  • shmem_longdouble_iput: Elements of type long double.
  • SHMEM_COMPLEX_IPUT: Elements of type complex of default size.
  • SHMEM_DOUBLE_IPUT: (Fortran) Elements of type double precision.
  • SHMEM_INTEGER_IPUT: Elements of type integer.
  • SHMEM_LOGICAL_IPUT: Elements of type logical.
  • SHMEM_REAL_IPUT: Elements of type real.
  • SHMEM_LOGICAL_IPUT: Elements of type logical.
  • SHMEM_REAL_IPUT: Elements of type real.

(no that's not a typo, SHMEM_LOGICAL_IPUT and SHMEM_REAL_IPUT really do show up twice in the list. the source material said it twice, so we're saying it twice. consistency icon behavior 💅)

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). 🎀

📝 NOTES 📝

  • See intro_shmem(3) for a definition of the term remotely accessible. yep, that's the whole notes section. go read it, it's important iykyk 🫶

🌈 EXAMPLES 🌈

Consider the following simple shmem_long_iput example for C/C++ programs.

#include <mpp/shmem.h>

main()
{
  short source[10] = { 1, 2, 3, 4, 5,
  6, 7, 8, 9, 10 };
  static short target[10];

  shmem_init();
  if (shmem_my_pe() == 0) {
    /* put 10 words into target on PE 1 */
    shmem_short_iput(target, source, 1, 2, 5, 1);
  }
  shmem_barrier_all(); /* sync sender and receiver */
  if (shmem_my_pe() == 1) {
    shmem_udcflush(); /* not required on IRIX systems */
    printf("target on PE %d is %d %d %d %d %d0, shmem_my_pe(),
    (int)target[0], (int)target[1], (int)target[2],
    (int)target[3], (int)target[4] );
  }
  shmem_barrier_all(); /* sync before exiting */
}

See also: intro_shmem(3) shmem_iget(3) shmem_put(3) shmem_quiet(3)

2003-2026, The Open MPI Community

and that's the whole page bestie, we ate and left no crumbs 👑 the copyright belongs to 2003-2026, The Open MPI Community, and this lil masterpiece is dated Sep 10, 2026 — it's SHMEM_LONGLONG_IPUT(3), from the Open MPI manual, forever and always. go forth and stride your data, main character. mwah 💋💖✨

📦 where this page comes from