SHMEM_DOUBLE_PUT_NBI(3)

💅 SHMEM_DOUBLE_PUT_NBI(3) — the nonblocking put girlies ✨

okay so bestie, welcome to the Open MPI edition of this page 🫶 this is your one-stop shop for the shmem_*_put_nbi family — the nonblocking put routines. They literally provide a method for copying data from a contiguous local data object to a data object on a specified PE. no cap. 💖

---

🌸 NAME 🌸

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)

— the nonblocking put routines 💅 they give you a whole method for copying data from a contiguous local data object over to a data object on a specified PE. iconic behavior, honestly.

---

✨ 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 vibe here: these routines return after posting the operation. like, they dip immediately, they do not wait around 💨 the operation is considered complete only after a subsequent call to shmem_quiet. and bestie, at the completion of shmem_quiet, the data has been copied into the dest array on the destination PE. periodt.

⚠️ but here's the tea: the delivery of data words into the data object on the destination PE may occur in any order. not only 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 ordering matters to you, fence between them, no cap. 🧚

The arguments are as follows, bestie:

• dest — the data object to be updated on the remote PE. this one must be remotely accessible. non-negotiable 💅
• source — the data object containing the data to be copied. that's your payload, your main character ✨
• nelems — number of elements in the dest and source arrays. it must be of type size_t for C. if you're on the Fortran side, 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. 🦋

And for the Fortran girlies: 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 try to be cute with it, just declare it properly 🙈

---

🔥 NOTES 🔥

honestly just go read intro_shmem(3) for a definition of the term remotely accessible — it's giving required reading, iykyk 📚

---

🌈 EXAMPLES 🌈

okay consider this simple example for C, it's lowkey adorable:

#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 posts the put and then hits shmem_quiet()? that's the moment the data actually lands in target on PE 1. then everybody meets at the barrier to sync sender and receiver, and PE 1 does the shmem_udcflush() — which, btw, is not required on Altix systems 😌 the whole thing is a full serve.

👀 SEE ALSO:

intro_shmem(3) shmem_quiet(3)

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community

---

and that's the page bestie, you ate 💅✨ stay nonblocking, stay quiet until shmem_quiet, and remember: this was the Open MPI SHMEM_DOUBLE_PUT_NBI(3) page, dated May 14, 2026 🎀🫶 slay responsibly! 🌸💖