SHMEM_PE_ACCESSIBLE(3)

✨ shmem_pe_accessible(3) ✨

okay so bestie, this one's an Open MPI moment 💅 and it's literally all about one tiny question: can I even talk to that PE or not? 🫶

🌸 NAME 🌸

shmem_pe_accessible — lowkey the vibe check for whether a processing element (PE) is accessible via SHMEM data transfer operations 🔥

---

🎀 SYNOPSIS 🎀

C bestie, you're up first:

#include <mpp/shmem.h>

int shmem_pe_accessible(int pe)

Fortran bestie, this one's for you:

INCLUDE "mpp/shmem.fh"

LOGICAL LOG, SHMEM_PE_ACCESSIBLE
INTEGER pe

LOG = SHMEM_PE_ACCESSIBLE(pe)

---

🦋 DESCRIPTION 🦋

so shmem_pe_accessible returns a value that tells you whether the calling PE is able to perform OpenSHMEM communication operations with the remote PE ✨ like, that's it, that's the whole function, and honestly? iconic 👑

---

⭐ RETURN VALUES ⭐

• C/C++ — the return value is 1 if the specified PE is a valid remote PE for SHMEM functions; otherwise, it is 0 💀 (yes, "otherwise,it" is how the original wrote it, no cap 🙈)
• Fortran — the return value is .TRUE. if the specified PE is a valid remote PE for SHMEM functions; otherwise, it is .FALSE. 🎀 (and yes, .FALSE.. with the double dot, that's literally what it says 😭)

---

👀 SEE ALSO: 👀

• intro_shmem(3)
• shmem_addr_accessible(3)

go read those next bestie, they're giving main character energy too 🌈

---

💜 COPYRIGHT 💜

2003-2026, The Open MPI Community

---

and that's the whole page, periodt 💅 the Open MPI girlies dated this one May 14, 2026 and it's filed under SHMEM_PE_ACCESSIBLE(3) — mwah, go slay your SHMEM comms bestie 🧚💖