MPI_WIN_DETACH(3)

📦
version 5.0.11 · 16 versions
, in arch rolling

💅 MPI_WIN_DETACH(3)

okay so bestie, this is the Open MPI page for MPI_Win_attach and MPI_Win_detach — the one-sided MPI calls that attach / detach a memory region to / from a window object for RMA operations. it's giving "let me just slide this memory over here" energy and honestly we love that for us 🫶

✨ SYNTAX ✨

🌸 C Syntax

#include <mpi.h>

MPI_Win_attach(MPI_Win win, void *base, MPI_Aint size)

MPI_Win_detach(MPI_Win win, void *base)

🌸 Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_WIN_ATTACH(WIN, BASE, SIZE, IERROR)
     <type> BASE(*)
     INTEGER(KIND=MPI_ADDRESS_KIND) SIZE
     INTEGER WIN, IERROR

MPI_WIN_DETACH(WIN, BASE, IERROR)
     <type> BASE(*)
     INTEGER WIN, IERROR

🌸 Fortran 2008 Syntax

USE mpi_f08
MPI_Win_attach(win, base, size, ierror)
     TYPE(MPI_Win), INTENT(IN) :: win
     TYPE(*), DIMENSION(..), INTENT(IN) :: base
     INTEGER(KIND=MPI_ADDRESS_KIND), INTENT(IN) :: size
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

MPI_Win_detach(win, base, ierror)
     TYPE(MPI_Win), INTENT(IN) :: win
     TYPE(*), DIMENSION(..), INTENT(IN) :: base
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

🎀 INPUT PARAMETERS 🎀

  • win — a window that was created with MPI_Win_create_dynamic ✨
  • base — initial address of window (choice).
  • size — size of window in bytes (nonnegative integer). keep it nonnegative bestie, that's the vibe check 💅

🦋 OUTPUT PARAMETERS 🦋

  • win — window object returned by the call (handle).
  • ierror — Fortran only: Error status (integer).
ngl win showing up in both the input and the output list is just how this page is written — we don't make the rules, we just report them faithfully 😭

🔥 DESCRIPTION 🔥

MPI_Win_attach is a one-sided MPI communication call used to attach a memory region of size bytes starting at address base to a window for RMA access. so basically you're like "hey window, this chunk of memory is yours now" and the window is like "slay, noted" 💖

The window win must have been created using MPI_Win_create_dynamic. no exceptions, no cap.

Multiple non-overlapping memory regions may be attached to the same dynamic window — go off, stack them regions 👑

Attaching overlapping memory regions to the same dynamic window is erroneous. 🚨 like, genuinely do not do that. that's the villain origin story.

If the base value used by MPI_Win_attach was allocated by MPI_Alloc_mem, the size of the window can be no larger than the value set by the MPI_Alloc_mem function. respect the limits, icon.

MPI_Win_detach can be used to detach a previously attached memory region from win. The memory address base and win must match arguments passed to a previous call to MPI_Win_attach — it's literally the "you two have to match" meme, no substitutions 🙈

🧚 NOTES 🧚

Use memory allocated by MPI_Alloc_mem to guarantee properly aligned window boundaries (such as word, double-word, cache line, page frame, and so on). alignment is self-care, periodt ✨

💀 ERRORS 💀

Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.

Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions.

Open MPI includes three predefined error handlers that can be used — the holy trinity of "something went wrong" 🕯️:

  • MPI_ERRORS_ARE_FATAL — Causes the program to abort all connected MPI processes. yeah. everything. gone. 💀
  • MPI_ERRORS_ABORT — An error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process. local process only, she's polite like that 💅
  • MPI_ERRORS_RETURN — Returns an error code to the application. the "we can talk about this" option 🫶

MPI applications can also implement their own error handlers by calling:

  • MPI_Comm_create_errhandler then MPI_Comm_set_errhandler
  • MPI_File_create_errhandler then MPI_File_set_errhandler
  • MPI_Session_create_errhandler then MPI_Session_set_errhandler or at MPI_Session_init
  • MPI_Win_create_errhandler then MPI_Win_set_errhandler
Note that MPI does not guarantee that an MPI program can continue past an error. 😭 like fr fr, don't count on it.

See the MPI man page for a full list of MPI error codes.

See the Error Handling section of the MPI-3.1 standard for more information.

2003-2026, The Open MPI Community 🌈

and that's the whole page bestie — page date Sep 11, 2026, straight from Open MPI, main character energy from top to bottom, no details left behind 💜✨🎀

📦 where this page comes from