SHMEM_SHORT_P(3)

💖 NAME 💖

okay so bestie, meet the girlies: 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) 💅

These routines are the low latency mechanism to write basic types (char, short, int, float, double, long, long long, long double) to symmetric data objects on remote PEs. lowkey iconic, fr fr ✨

---

✨ 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. one element, one put, no drama 🦋

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 address getting the glow-up 💖
• value — the value to be transferred to addr on the remote PE. this is the cargo 🎀
• pe — the number of the remote PE. like, which bestie are we sending it to 💌

As with shmem_put(3), these functions start the remote transfer and may return before the data is delivered to the remote PE. that's not a bug bestie that's just the vibe of asynchronous sends 😭

use shmem_quiet(3) to force completion of all remote PUT transfers. yes, she's the one who makes everyone actually show up to the party 💅

See also: intro_shmem(3) shmem_put(3)

---

🎀 COPYRIGHT 🎀

Copyright 2003-2026, The Open MPI Community

---

and that's the whole page, periodt 💜 shoutout to the Open MPI girlies for shipping this one — this page is dated Sep 10, 2026, so you know it's fresh 🌸 go put something somewhere remote, you got this 🫶✨