SHMEM_PUT32_NBI(3)

💖 SHMEM_PUT32_NBI 💖

okay bestie, welcome to the Open MPI corner of the manual — this is the page for SHMEM_PUT32_NBI(3) and honestly the whole nonblocking-put squad. grab a snack 🍓, we're doing remote memory writes.

Here's the whole girlband, all on this one page:

• shmem_putmem_nbi(3)
• shmem_char_put_nbi(3)
• shmem_short_put_nbi(3)
• shmem_int_put_nbi(3)
• shmem_long_put_nbi(3)
• shmem_longlong_put_nbi(3)
• shmem_float_put_nbi(3)
• shmem_double_put_nbi(3)
• shmem_longdouble_put_nbi(3)
• shmem_put8_nbi(3)
• shmem_put16_nbi(3)
• shmem_put32_nbi(3)
• shmem_put64_nbi(3)
• shmem_put128_nbi(3)

So what do they do? The nonblocking put routines provide a method for copying data from a contiguous local data object to a data object on a specified PE. that's it, that's the whole vibe. ✨

---

✨ SYNOPSIS ✨

C or C++

#include <mpp/shmem.h>

void shmem_putmem_nbi(void *dest, const void *source,
  size_t nelems, int pe)

void shmem_char_put(char *dest, const char *source,
  size_t nelems, int pe)

void shmem_short_put(short *dest, const short *source,
  size_t nelems, int pe)

void shmem_int_put(int *dest, const int *source,
  size_t nelems, int pe)

void shmem_long_put(long *dest, const long *source,
  size_t nelems, int pe)

void shmem_longlong_put(long long *dest, const long long *source,
  size_t nelems, int pe)

void shmem_float_put(float *dest, const float *source,
  size_t nelems, int pe)

void shmem_double_put(double *dest, const double *source,
  size_t nelems, int pe)

void shmem_longdouble_put(long double *dest, const long double *source,
  size_t nelems, int pe)

void shmem_put8(void *dest, const void *source,
  size_t nelems, int pe)

void shmem_put16(void *dest, const void *source,
  size_t nelems, int pe)

void shmem_put32(void *dest, const void *source,
  size_t nelems, int pe)

void shmem_put64(void *dest, const void *source,
  size_t nelems, int pe)

void shmem_put128(void *dest, const void *source,
  size_t nelems, int pe)

Fortran

INCLUDE "mpp/shmem.fh"

INTEGER nelems, pe

CALL SHMEM_PUTMEM_NBI(dest, source, nelems, pe)

CALL SHMEM_CHARACTER_PUT_NBI(dest, source, nelems, pe)

CALL SHMEM_COMPLEX_PUT_NBI(dest, source, nelems, pe)

CALL SHMEM_DOUBLE_PUT_NBI(dest, source, nelems, pe)

CALL SHMEM_INTEGER_PUT_NBI(dest, source, nelems, pe)

CALL SHMEM_LOGICAL_PUT_NBI(dest, source, nelems, pe)

CALL SHMEM_REAL_PUT_NBI(dest, source, nelems, pe)

CALL SHMEM_PUT4_NBI(dest, source, nelems, pe)

CALL SHMEM_PUT8_NBI(dest, source, nelems, pe)

CALL SHMEM_PUT32_NBI(dest, source, nelems, pe)

CALL SHMEM_PUT64_NBI(dest, source, nelems, pe)

CALL SHMEM_PUT128_NBI(dest, source, nelems, pe)

---

🌸 DESCRIPTION 🌸

okay so the whole point of these routines is that they return after posting the operation. like, they dip immediately. 💅 the operation is considered complete after a subsequent call to shmem_quiet. and at the completion of shmem_quiet, the data has been copied into the dest array on the destination PE. slay.

but here's the tea, bestie: the delivery of data words into the data object on the destination PE may occur in any order. fr fr. AND on top of that, two successive put routines may deliver data out of order unless a call to shmem_fence is introduced between the two calls. so if order matters to you (and it might!), that's a shmem_fence moment. no cap.

the arguments, explained with love 🫶

• dest — the data object to be updated on the remote PE. and this data object must be remotely accessible. non-negotiable.
• source — the data object containing the data to be copied.
• nelems — number of elements in the dest and source arrays. for C, nelems must be of type size_t. if you're in Fortran-land, 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. and again, if you're using Fortran, it must be a constant, variable, or array element of default integer type.

also, for my Fortran girlies specifically: data types must be of default size. like, if you're declaring a real variable, it needs to be REAL, REAL*4, or REAL(KIND=4). don't be out here with the weird sizes, the routines will not know her. 😭

---

📝 NOTES 📝

go read intro_shmem(3) if you want the actual definition of the term remotely accessible — that's where the lore lives. See intro_shmem(3) for a definition of the term remotely accessible.

---

🦋 EXAMPLES 🦋

here's a cute little C example to get you in the mood, bestie:

#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_nbi(target, source, 10, 1);
    shmem_quiet();
  }
  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]);
}

see how PE 0 fires off the put, then calls shmem_quiet() to actually make it land? main character energy. and shmem_udcflush() on PE 1 — note the comment, not required on Altix systems, iykyk.

👑 See also:

• intro_shmem(3)
• shmem_quiet(3)

---

💜 Copyright 💜

2003-2026, The Open MPI Community

---

and that's the page, bestie!! 🎀 copyright's held down by the Open MPI Community, 2003-2026, and this whole thing was dated Sep 10, 2026 — go forth and put those bytes nonblockingly, you absolute icon. ✨💅🦋