SHMEM_LONG_PUT(3)

📦
version 5.0.10 · 4 versions
, in ubuntu stonking

🎀 NAME 🎀

hiii bestie 💖 you just opened the SHMEM_LONG_PUT(3) page, and honestly? you're in the right place. this one manpage is basically a whole group chat of sibling functions, and every single one of them does the exact same iconic thing: transfers data to a specified processing element (PE). periodt. 👑

here's the whole squad, all of them covered right here on this page:

no cap, they're all the same move with different outfits on. 💅

✨ SYNOPSIS ✨

💜 C or C++

first, the vibe: pull in the header.

#include <mpp/shmem.h>

then pick your flavor bestie:

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

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

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

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

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

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

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

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

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

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

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

🦋 Fortran

and for the Fortran girlies, include the file and declare your ints:

INCLUDE "mpp/shmem.fh"

INTEGER len, pe

then take your pick 🎀:

CALL SHMEM_CHARACTER_PUT(target, source, len, pe)

CALL SHMEM_COMPLEX_PUT(target, source, len, pe)

CALL SHMEM_DOUBLE_PUT(target, source, len, pe)

CALL SHMEM_INTEGER_PUT(target, source, len, pe)

CALL SHMEM_LOGICAL_PUT(target, source, len, pe)

CALL SHMEM_PUT(target, source, len, pe)

CALL SHMEM_PUT4(target, source, len, pe)

CALL SHMEM_PUT8(target, source, len, pe)

CALL SHMEM_PUT32(target, source, len, pe)

CALL SHMEM_PUT64(target, source, len, pe)

CALL SHMEM_PUT128(target, source, len, pe)

CALL SHMEM_PUTMEM(target, source, len, pe)

CALL SHMEM_REAL_PUT(target, source, len, pe)

💅 DESCRIPTION 💅

okay so here's the tea ☕ — these routines take nelems elements of the data object sitting at address source on the calling PE, and they yeet them over to the data object at address target on the remote PE pe. 🚀

here's the part you need to internalize though: these routines start the remote transfer and may return before the data is delivered to the remote PE. so like. it left the group chat. it has not necessarily arrived yet. 😭

and listen — the delivery of data into the data object on the destination PE, coming from different put calls, may occur in any order. because of this, two successive put operations may deliver data out of order unless a call to shmem_fence(3) is introduced between the two calls. so if you need order, you better fence those calls apart, bestie. no fence, no vibes. 🚧

🍓 the arguments

  • target — the data object that's getting updated on the remote PE. important: this data object must be remotely accessible. if it's not, we're not doing this. 🙅
  • source — the data object holding the data that's gonna be copied.
  • len — the number of elements in the target and source arrays. len must be of type integer. if you're doing Fortran, it has to be a constant, a variable, or an array element of default integer type.
  • pe — the PE number of the remote PE. pe must be of type integer. and again for the Fortran girlies: it must be a constant, a variable, or an array element of default integer type.

👑 typing constraints (the vibe check for your data)

the target and source data objects have to conform to certain typing constraints, and here's the list fr fr:

  • shmem_putmem — Fortran: any noncharacter type. C: any data type. and heads up, len is scaled in bytes.
  • shmem_put4, shmem_put32 — any noncharacter type that has a storage size equal to 32 bits.
  • shmem_put8, shmem_put64 — any noncharacter type that has a storage size equal to 64 bits.
  • shmem_put128 — any noncharacter type that has a storage size equal to 128 bits.
  • shmem_short_put — elements of type short.
  • shmem_int_put — elements of type int.
  • shmem_long_put — elements of type long.
  • shmem_longlong_put — elements of type long long.
  • shmem_float_put — elements of type float.
  • shmem_double_put — elements of type double.
  • shmem_longdouble_put — elements of type long double.
  • SHMEM_CHARACTER_PUT — 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_PUT — elements of type complex of default size.
  • SHMEM_DOUBLE_PUT — (Fortran) elements of type double precision.
  • SHMEM_INTEGER_PUT — elements of type integer.
  • SHMEM_LOGICAL_PUT — elements of type logical.
  • SHMEM_REAL_PUT — 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 get cute with it. 🌸

🌈 EXAMPLES 🌈

here's a shmem_put moment, written for C/C++ programs — look how pretty 💖:

#include <stdio.h>
#include <mpp/shmem.h>

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

  if (shmem_my_pe() == 0) {
    /* put 10 words into target on PE 1 */
    shmem_long_put(target, source, 10, 1);
  }
  shmem_barrier_all();  /* sync sender and receiver */
  if (shmem_my_pe() == 1)
    shmem_udcflush();  /* not required on Altix systems */
  printf("target[0] on PE %d is %d\n", shmem_my_pe(), target[0]);
}

notice that shmem_barrier_all() doing the heavy lifting as the sync sender-and-receiver moment, and that shmem_udcflush() not required on Altix systems note? yeah, that's there too. don't skip it. 🔥

👀 See also

2003-2026, The Open MPI Community

and that's the whole page, bestie!! 🦋 one last lil sign-off from the footer energy: this whole thing is brought to you by Open MPI, dated Sep 10, 2026, filed under SHMEM_LONG_PUT(3) — stay remotely accessible and go fence your puts, ily!! ✨💜🎀

📦 where this page comes from