SHMEM_LONGLONG_P(3)

🎀 SHMEM_LONGLONG_P(3) — an Open MPI manual page, but make it make sense 🎀

Okay bestie, this is the Open MPI manual page for SHMEM_LONGLONG_P(3) and its little function friend group. It’s giving low-latency put energy, and honestly? Iconic. 💅

🌸 NAME 🌸

shmem_char_p(3), shmem_float_p(3), shmem_int_p(3), shmem_long_p(3), shmem_short_p(3), shmem_longlong_p(3), shmem_longdouble_p(3) — these routines provide a low latency mechanism to write basic types (char, short, int, float, double, long, long long, long double) to symmetric data objects on remote PEs.

✨ SYNOPSIS ✨

C or C++:

#include <mpp/shmem.h>

void shmem_char_p(char *addr, char value, int pe)

void shmem_short_p(short *addr, short value, int pe)

void shmem_int_p(int *addr, int value, int pe)

void shmem_long_p(long *addr, long value, int pe)

void shmem_longlong_p(long long *addr, long long value, int pe)

void shmem_float_p(float *addr, float value, int pe)

void shmem_double_p(double *addr, double value, int pe)

void shmem_longdouble_p(long double *addr, long double value, int pe)

💖 DESCRIPTION 💖

These routines provide a very low latency put capability for single elements of most basic types. Like, it’s just one little value getting sent to a remote PE’s data object, and the efficiency is lowkey the main character. 🫶

The arguments are as follows:

• addr — the remotely accessible array element or scalar data object which will receive the data on the remote PE.
• value — the value to be transferred to addr on the remote PE.
• pe — the number of the remote PE.

As with shmem_put(3), these functions start the remote transfer and may return before the data is delivered to the remote PE. Use shmem_quiet(3) to force completion of all remote PUT transfers. ⚠️

👀 SEE ALSO 👀

• intro_shmem(3)
• shmem_put(3)

📜 COPYRIGHT 📜

2003-2026, The Open MPI Community

---

Mwah 💋 — this page came from the Open MPI manual, dated May 14, 2026, for SHMEM_LONGLONG_P(3). Stay slay, bestie. 🎀