SHMEM_IPUT64(3)
π NAME π
shmem_iput64 and her whole girl squad of strided-put besties, fr fr π
Okay so this is the manual page for a whole family of related routines: shmem_complex_iput(3), shmem_double_iput(3), shmem_float_iput(3), shmem_int_iput(3), shmem_integer_iput(3), shmem_iput4(3), shmem_iput8(3), shmem_iput32(3), shmem_iput64(3), shmem_iput128(3), shmem_logical_iput(3), shmem_long_iput(3), shmem_longdouble_iput(3), shmem_longlong_iput(3), shmem_real_iput(3), and shmem_short_iput(3) β and what do they do? They transfer strided data to a specified processing element (PE). That's the whole vibe. β¨
This one lives in the Open MPI collection of manual pages, and tbh it's giving "I just need to poke some scattered values into my friend's memory and leave immediately." π¦
β¨ SYNOPSIS β¨
C or C++ π
#include <mpp/shmem.h>
void shmem_double_iput(double *target, const double *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_float_iput(float *target, const float *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_int_iput(int *target, const int *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_iput32(void *target, const void *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_iput64(void *target, const void *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_iput128(void *target, const void *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_long_iput(long *target, const long *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
void shmem_longdouble_iput(long double *target,
const long double *source, ptrdiff_t tst, ptrdiff_t sst,
size_t len, int pe)
void shmem_longlong_iput(long long *target,
const long long *source, ptrdiff_t tst, ptrdiff_t sst,
size_t len, int pe)
void shmem_short_iput(short *target, const short *source,
ptrdiff_t tst, ptrdiff_t sst, size_t len, int pe)
Fortran π§
INCLUDE "mpp/shmem.fh"
INTEGER tst, sst, len, pe
CALL SHMEM_COMPLEX_IPUT(target, source, tst, sst, len,
& pe)
CALL SHMEM_DOUBLE_IPUT(target, source, tst, sst, len,
& pe)
CALL SHMEM_INTEGER_IPUT(target, source, tst, sst, len,
& pe)
CALL SHMEM_IPUT4(target, source, tst, sst, len, pe)
CALL SHMEM_IPUT8(target, source, tst, sst, len, pe)
CALL SHMEM_IPUT32(target, source, tst, sst, len, pe)
CALL SHMEM_IPUT64(target, source, tst, sst, len, pe)
CALL SHMEM_IPUT128(target, source, tst, sst, len, pe)
CALL SHMEM_LOGICAL_IPUT(target, source, tst, sst, len,
& pe)
CALL SHMEM_REAL_IPUT(target, source, tst, sst, len, pe)
π DESCRIPTION π
So the shmem_iput routines read the elements of a local array (source) and write them into a remote array (target) sitting on the PE you name in pe. And here's the part everyone needs to internalize: these routines return when the data has been copied out of the source array on the local PE β but not necessarily before the data has been delivered to the remote data object. So don't be out here acting like "it returned" means "it arrived." It does not. π
Here are the arguments, bestie, one by one:
targetβ the array that gets updated on the remote PE. This data object must be remotely accessible. Non-negotiable, babes.sourceβ the array holding the data you're copying.tstβ the stride between consecutive elements of the target array. It gets scaled by the element size of the target array, and a value of1means the data is contiguous. Alsotstmust be of type integer. If you're in Fortran, it has to be a default integer value.sstβ the stride between consecutive elements of the source array. Same deal: scaled by the element size of the source array, and1means contiguous.sstmust be of type integer, and in Fortran it must be a default integer value.lenβ the number of elements in the target and source arrays.lenmust be of type integer, and in Fortran it must be a constant, variable, or array element of default integer type.peβ the PE number of the remote PE.pemust be of type integer, and in Fortran it must be a constant, variable, or array element of default integer type.
πΈ the typing constraints (read these, they're the vibe check) πΈ
The target and source data objects have to conform to typing constraints, and they are as follows:
shmem_iput32,shmem_iput4: any noncharacter type that has a storage size equal to 32 bits.shmem_iput64,shmem_iput8: any noncharacter type that has a storage size equal to 64 bits.shmem_iput128: any noncharacter type that has a storage size equal to 128 bits.shmem_short_iput: elements of typeshort.shmem_int_iput: elements of typeint.shmem_long_iput: elements of typelong.shmem_longlong_iput: elements of typelong long.shmem_float_iput: elements of typefloat.shmem_double_iput: elements of typedouble.shmem_longdouble_iput: elements of typelong double.SHMEM_COMPLEX_IPUT: elements of typecomplexof default size.SHMEM_DOUBLE_IPUT: (Fortran) elements of typedouble precision.SHMEM_INTEGER_IPUT: elements of typeinteger.SHMEM_LOGICAL_IPUT: elements of typelogical.SHMEM_REAL_IPUT: elements of typereal.SHMEM_LOGICAL_IPUT: elements of typelogical.SHMEM_REAL_IPUT: elements of typereal.
(Yeah, SHMEM_LOGICAL_IPUT and SHMEM_REAL_IPUT each get listed twice up there. That's just how the page reads β iconic of it, honestly. π)
And if you're using Fortran, data types must be of default size. Example: a real variable has to be declared as REAL, REAL*4 or REAL(KIND=4). π
π«Ά NOTES π«Ά
Wanna know what "remotely accessible" actually means? Run, don't walk, to intro_shmem(3) β it has the whole definition. β¨
π₯ EXAMPLES π₯
Okay so consider this simple shmem_long_iput example for C/C++ programs:
#include <mpp/shmem.h>
main()
{
short source[10] = { 1, 2, 3, 4, 5,
6, 7, 8, 9, 10 };
static short target[10];
shmem_init();
if (shmem_my_pe() == 0) {
/* put 10 words into target on PE 1 */
shmem_short_iput(target, source, 1, 2, 5, 1);
}
shmem_barrier_all(); /* sync sender and receiver */
if (shmem_my_pe() == 1) {
shmem_udcflush(); /* not required on IRIX systems */
printf("target on PE %d is %d %d %d %d %d0, shmem_my_pe(),
(int)target[0], (int)target[1], (int)target[2],
(int)target[3], (int)target[4] );
}
shmem_barrier_all(); /* sync before exiting */
}
See also, bestie β go read these too, they're all in the group chat:
intro_shmem(3)shmem_iget(3)shmem_put(3)shmem_quiet(3)
π COPYRIGHT π
2003-2026, The Open MPI Community π«Ά
And that's the page!! π This was SHMEM_IPUT64(3) from the Open MPI fam, last touched Sep 10, 2026 β go put some strided data somewhere, slay, and remember to sync before you exit. Periodt. β¨ππ¦
π¦ where this page comes from
- ubuntu stonking: openmpi-doc 5.0.10-6 Β· other
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms