SHMEM_LONG_PUT_NBI(3)

πŸ“¦
version 5.0.10 Β· 4 versions
, in ubuntu stonking

πŸŽ€ NAME πŸŽ€

okay bestie, gather round, because this is the whole nonblocking put squad and they're all iconic πŸ’…

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, and they're giving "copy your data from a contiguous local data object over to a data object on a PE you picked" energy. No cap.


✨ 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 πŸ’–

So here's the tea, bestie: these routines return after posting the operation. That's literally it. They said "posting it, bye πŸ‘‹" and they dipped.

The operation is considered complete after a subsequent call to shmem_quiet. At the completion of shmem_quiet, the data has been copied into the dest array on the destination PE. Slay.

But lowkey, heads up: the delivery of data words into the data object on the destination PE may occur in any order. And it gets messier β€” two successive put routines may deliver data out of order unless a call to shmem_fence is introduced between the two calls. The way that ordering isn't guaranteed is so real 😭

🌈 The arguments

  • dest β€” the data object to be updated on the remote PE. This data object must be remotely accessible.
  • source β€” the data object containing the data to be copied.
  • nelems β€” number of elements in the dest and source arrays. nelems must be of type size_t for C. For Fortran girlies: it must be a constant, variable, or array element of default integer type.
  • pe β€” the PE number of the remote PE. pe must be of type integer. For Fortran girlies: it must be a constant, variable, or array element of default integer type.
Also if you're in 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 be out here doing too much πŸ’…

πŸ“ NOTES πŸ“

See intro_shmem(3) for a definition of the term remotely accessible. iykyk ✨


πŸ”₯ EXAMPLES πŸ”₯

ok so picture this simple C example, main character energy only:

#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 also:

intro_shmem(3) shmem_quiet(3)


2003-2026, The Open MPI Community


kk that's the whole page bestie 🫢 this was SHMEM_LONG_PUT_NBI(3) from Open MPI, and the date on the tin is Sep 10, 2026. go forth and put nonblockingly, periodt πŸ’œβœ¨

πŸ“¦ where this page comes from