search

huttered40 / critter

Critical path analysis of MPI parallel programs
BSD 2-Clause "Simplified" License
2 stars 1 forks source link

Standalone use of MPI_Waitany is non-functional #26

Closed huttered40 closed 4 years ago

huttered40 commented 5 years ago

Because MPI_Waitall uses MPI_Waitany, the latter used by itself (called directly from the user code) is not functional because we have no idea how to know that the other process in the initial nonblocking communication is also waiting on it. If not, we get a deadlock.

Perhaps the only other option is just tell the user straight-up that we do not propogate the critical path with this routine?

huttered40 commented 4 years ago

Fixed.