MPIX_Stream_progress(3)

πŸ“¦
version 5.0.1 Β· 4 versions
, in nixos 26.05, ubuntu stonking

πŸ’– NAME πŸ’–

MPIX_Stream_progress β€” bestie, this one invokes progress on the given stream ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int MPIX_Stream_progress(MPIX_Stream stream)

πŸŽ€ INPUT PARAMETERS πŸŽ€

  • stream β€” the stream object (it's a handle, okay, it's giving handle energy) πŸ’…

πŸ‘‘ THREAD AND INTERRUPT SAFETY πŸ‘‘

So this routine is thread-safe, no cap. That means multiple threads can use it at the same time and you do not need to bring your own thread locks β€” the routine handles that for you. Slay.

But β€” and hear me out β€” it is not interrupt safe. 😭 Typically that's because it uses memory allocation routines like malloc, or other non-MPICH runtime routines that are themselves not interrupt-safe. So like, threads yes, interrupts no. Periodt.


🧚 NOTES FOR FORTRAN 🧚

Every MPI routine in Fortran (except for MPI_WTIME and MPI_WTICK) has an extra argument called ierr tacked onto the end of the argument list. ierr is an integer and it means the exact same thing as the return value of the routine in C.

In Fortran, MPI routines are subroutines, and you invoke them with the call statement. That's just how it is, iykyk.

Also, all MPI objects (like MPI_Datatype, MPI_Comm) are of type INTEGER in Fortran. Yes, all of them. πŸ’œ


🌈 ERRORS 🌈

Every MPI routine (except MPI_Wtime and MPI_Wtick) returns an error value β€” for C routines it's the value of the function, and for Fortran routines it lives in that last argument. Before the value comes back to you, the current MPI error handler gets called.

⚠️ By default, this error handler aborts the MPI job. Like, whole thing, gone. πŸ™ˆ

You can change the error handler though:

  • MPI_Comm_set_errhandler β€” for communicators
  • MPI_File_set_errhandler β€” for files
  • MPI_Win_set_errhandler β€” for RMA windows

The MPI-1 routine MPI_Errhandler_set may also be used, but its use is deprecated (so don't come for me if you use the old one, bestie, it's giving legacy). The predefined error handler MPI_ERRORS_RETURN may be used to cause error values to be returned instead.

Note that MPI does not guarantee that an MPI program can continue past an error; however, MPI implementations will attempt to continue whenever possible. Fingers crossed energy. 🫢

Here's what you might get back:

  • MPI_SUCCESS β€” no error, the MPI routine completed successfully. Iconic. We love to see it. πŸ’–
  • MPI_ERR_OTHER β€” other error; use MPI_Error_string to get more information about this error code. So like, go read about it, k? 😭

That's the whole page, babe. This gem lives in the MPI manual, this version is dated 4/10/2026, and yes, the page is literally called MPIX_Stream_progress(3). Go invoke some progress on that stream. πŸ’…βœ¨πŸŒΈ

πŸ“¦ where this page comes from