SHMEM_LONGLONG_PUT_NBI(3)

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

βœ¨πŸ’… NAME πŸ’…βœ¨

okay so bestie, this page is a whole squad of nonblocking put routines and they all show up together:

  • 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)

and the vibe is: the nonblocking put routines provide a method for copying data from a contiguous local data object to a data object on a specified PE. 🫢

(this is the Open MPI edition of the page, SHMEM_LONGLONG_PUT_NBI(3), just so you know who's hosting the party πŸŽ€)


🌸 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 here's the tea: the routines return after posting the operation. like, they do NOT wait around for it to actually land, they just yeet it and dip. πŸƒβ€β™€οΈπŸ’¨

the operation is considered complete after a subsequent call to shmem_quiet(#shmem-quiet). at the completion of shmem_quiet(3), the data has been copied into the dest array on the destination PE. slay. βœ…

⚠️ but listen, bestie, the delivery of data words into the data object on the destination PE may occur in any order. and furthermore, two successive put routines 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 gotta fence it. no cap. 🚧😭

the arguments, one by one πŸŽ€

  • dest β€” the data object to be updated on the remote PE. this data object must be remotely accessible. (yes that's a real requirement, not a suggestion πŸ’…)
  • 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. if you're using Fortran, 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.

if you are 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). ✨


πŸ““ NOTES πŸ““

see intro_shmem(3) for a definition of the term remotely accessible. iykyk 🫢


🌈 EXAMPLES 🌈

consider this simple example for C. πŸ“

#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


and that's the whole page, bestie πŸ’‹ it came bundled with the Open MPI manual and it's dated Sep 10, 2026 β€” go forth and put your long longs nonblockingly, you absolute icon πŸ‘‘βœ¨πŸ’œ

πŸ“¦ where this page comes from