SHMEM_PUT128(3)

📦
version 5.0.10 · 4 versions
, in ubuntu stonking

💖 SHMEM_PUT128(3) 💖

okay bestie so this is the Open MPI manual page for the whole put squad — shmem_put128 and literally all of its little siblings. Same energy, different data types. Let's get into it ✨

This page covers all of these icons right here 💅

...and the vibe of every single one? Transfers data to a specified processing element (PE). That's the whole plot. 🎀

✨ SYNOPSIS ✨

C or C++ 🫶

#include <mpp/shmem.h>

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 🌸

INCLUDE "mpp/shmem.fh"

INTEGER len, pe

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 🦋

So here's the tea ☕ These routines take nelems elements of the data object sitting at address source on the PE that's calling, and they yeet them over to the data object at address target on the remote PE pe. 💌

Heads up bestie: these routines start the remote transfer and may return before the data is actually delivered to the remote PE. It's giving "sent the text, they haven't read it yet" energy. 😭

And lowkey the plot twist: the delivery of data into the object on the destination PE from different put calls may occur in any order. Which means two successive puts can land out of order unless you sneak a call to shmem_fence(3) in between them. No fence, no order. Periodt. 🧚

The arguments 💜

  • target — the data object that's getting updated on the remote PE. This one absolutely must be remotely accessible, no exceptions.
  • source — the data object holding the data that's getting copied.
  • len — the number of elements in the target and source arrays. It has to be of type integer. And if you're in Fortran land, it's gotta be a constant, variable, or array element of default integer type.
  • pe — the PE number of the remote PE. Also integer. And in Fortran, same deal: constant, variable, or array element of default integer type.

Typing constraints (aka the rules, don't fight them) 🎀

The target and source data objects have to conform to certain typing constraints, and they are as follows:

  • shmem_putmem — Fortran: any noncharacter type. C: any data type. 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. (not me — the manpage said it 🫣)
  • 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.

Also, if you're doing Fortran, data types must be of default size. Like, a real variable has to be declared as REAL, REAL*4, or REAL(KIND=4). That's the assignment, don't deviate bestie. 💅

🌸 EXAMPLES 🌸

Here's a shmem_put example for all my C/C++ girlies:

#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]);
}

Look at her go. She's serving synchronized PEs. 👑

See also 🦋

2003-2026, The Open MPI Community

and that's the whole page bestie, you ate it up fr fr 💖✨ the Open MPI girlies wrote this one, SHMEM_PUT128(3) said Sep 10, 2026 on her way out — iconic behavior, no notes, slay 🎀🫶 mwah 💅

📦 where this page comes from