SHMEM_SHORT_P(3)

💅 SHMEM_SHORT_P 💅

okay so bestie, welcome to the <p>-suffix corner of Open MPI's shmem world — this is the shmem_short_p(3) page (and like, it's literally a whole friend group of pages all sharing one doc), straight out of Open MPI. Buckle up, we're putting tiny little values on remote PEs and we're doing it fast. 🦋

🌸 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. it's giving "small put, big energy" ✨

---

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

like, pick your type, pick your PE, that's the whole vibe 💅

---

💖 DESCRIPTION 💖

These routines provide a very low latency put capability for single elements of most basic types. not a whole array, not a whole vibe — one element, delivered with main character 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. it's the landing spot, the destination, the receiving end of the friendship 🫶
• value — the value to be transferred to addr on the remote PE. this is the actual thing you're yeeting over there 💌
• pe — the number of the remote PE. yes bestie, you gotta say which PE, we're not mind readers 😭

⚠️ okay important one: as with shmem_put(3), these functions start the remote transfer and may return before the data is delivered to the remote PE. so like… it left your hands, doesn't mean it's arrived. use shmem_quiet(3) to force completion of all remote PUT transfers. no cap, don't skip the quiet if you actually need the data to be there. 🔥

---

👀 SEE ALSO: 👀

• intro_shmem(3)
• shmem_put(3)

---

🌈 COPYRIGHT 🌈

2003-2026, The Open MPI Community

---

and that's the page bestie!! 🎀 mwah, go forth and put your little shorts on remote PEs responsibly 💜

~ with love from the Open MPI squad, dated May 14, 2026 — catch you in the next manpage, iykyk ⭐