SHMEM_INT_P(3)
π SHMEM_INT_P β the put-something-somewhere-else page (Open MPI manual, bestie)
okay so this is SHMEM_INT_P(3) from the Open MPI manual, and it's actually a whole little fam of functions, not just the int one. The crew is:
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)
and what they do is give you 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. yes, all of those types, they really did that β¨
β¨ 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, one include, eight functions, zero drama π
πΈ DESCRIPTION πΈ
These routines provide a very low latency put capability for single elements of most basic types. it's giving "one value, one destination, no extra steps" 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 lil mailbox on the other side π«Άvalueβ the value to be transferred toaddron the remote PE. this is the actual payload, the main character of the operation βpeβ the number of the remote PE. gotta know where you're sending it, iykyk
β οΈ okay bestie, 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's asynchronous, don't panic when the value isn't there yet π
Use shmem_quiet(3) to force completion of all remote PUT transfers. that's your "okay everyone chill, let it land" call π
π¦ SEE ALSO π¦
intro_shmem(3)shmem_put(3)
go read those next, they're iconic too π
π COPYRIGHT π
2003-2026, The Open MPI Community
and that's the whole vibe check, bestie π this page was living under the Open MPI banner with source/version info dated May 14, 2026, filed under SHMEM_INT_P(3) β slay, periodt π
π¦ where this page comes from
- arch rolling: nvhpc-comm-libs 26.9-1 Β· LicenseRef-NVIDIA-HPC-SDK
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms