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

Jeff Hammond jeff.science at gmail.com
Tue Feb 9 20:02:59 CST 2016


On Tuesday, February 9, 2016, Jed Brown <jed at jedbrown.org> wrote:

> Rob Latham <robl at mcs.anl.gov <javascript:;>> 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.
>

Or extend Casper to support MPI IO... :-)

Jeff


-- 
Jeff Hammond
jeff.science at gmail.com
http://jeffhammond.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20160209/ea433871/attachment.html>
-------------- next part --------------
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss


More information about the discuss mailing list