If you do not explicitly enabled asynchronous progress (which btw is only supported by some of the BTLs), there will be little support for asynchronous progress in Open MPI. Indeed, as long as the library is not in an MPI call, all progress is stalled, no matching is done, and the only possible progress is the one done outside the OMPI framework (such as network-level RMA).
The ORTE progress thread only help during the setup of the runtime, it has no impact on the MPI communication. The fact that OPAL supports threads, simply means that the library has been compiled in a thread-safe way. This thread safety is then enabled at runtime, based on the arguments provided during MPI initialization (MPI_Init / MPI_Init_thread). George. On Tue, Jan 24, 2017 at 5:45 AM, Cyril Bordage <cyril.bord...@inria.fr> wrote: > Hello, > > I would like to see how the overlapping between communications and > computations is done in some applications. And I would like to be able > to prevent it. > In this purpose, is it possible to disable the progress engine and have > the application nearly as if there was no asynchronous communications? > > Since I am not familiar with ompi terminology, I would like to know what > the thread support section "OPAL support: yes, OMPI progress: no, ORTE > progress: yes" in impi_info means. > > Thank you. > > > Cyril. > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
