[mpich-discuss] MPI I/O spilt collective implementation: MPI_File_write_all_begin blocking or non-blocking?

[pramod kumbhar]

thanks! I see expected behaviour by setting MPICH_ASYNC_PROGRESS  (mpich
compiled with --enable-threads=multiple)

On Tue, Feb 9, 2016 at 10:22 PM, Jed Brown <jed at jedbrown.org> wrote:

> Rob Latham <robl at mcs.anl.gov> writes:
> > MPICH takes a weak interpretation of the progress rule, but one can
> > emulate strict interpretation by spawning a thread whose one job in life
> > is to call MPI_Test repeatedly.
>
> ... or define the MPICH_ASYNC_PROGRESS environment variable.
>
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20160211/2124f157/attachment.html>
-------------- next part --------------
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss