MPIX_Stream_progress(3)
π 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 communicatorsMPI_File_set_errhandlerβ for filesMPI_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; useMPI_Error_stringto 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
- nixos 26.05: mpich 5.0.1
- ubuntu stonking: mpich-doc 5.0.1-9 Β· other
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms