SHMEM_LONG_P(3)

🎀 NAME 🎀

okay bestie, this is Open MPI's SHMEM_LONG_P(3) page, and it's giving low-latency communication realness ✨

These routines — shmem_char_p(3), shmem_float_p(3), shmem_int_p(3), shmem_long_p(3), shmem_short_p(3), shmem_longlong_p(3), and shmem_longdouble_p(3) — 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. no cap 💅

---

🌸 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. it's giving "send one little value and make it iconic" energy 👑

The arguments are as follows:

• addr — the remotely accessible array element or scalar data object which will receive the data on the remote PE. that's the destination bestie 🎯
• value — the value to be transferred to addr on the remote PE. yes, the actual payload 💌
• pe — the number of the remote PE. you gotta know where it's going 📍

⚠️ important vibe check: 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. literally do not skip this part, bestie 😭

---

🌈 SEE ALSO 🌈

go peek at these, iykyk:

• intro_shmem(3)
• shmem_put(3)

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community

okay that’s the whole page, bestie — from Open MPI, dated May 14, 2026. 💖✨🫶