[mpiwg-ft] Ticket #324 Reading Slides

George Bosilca bosilca at icl.utk.edu
Wed May 20 17:53:56 CDT 2015


I understand the interest in scoping the abort to a single set of
processes. However, without support for detecting that some processes have
disappeared (failure or abort) I don't see how you can use this for
anything constructive. Thus, I am confused by this proposal as it seems to
lack a second part where the processes outside of the MPI_ABORT scope deal
with the newly defined behavior.

Can you be a little bit more explicit on how this scoped MPI_ABORT, as
defined in this ticket, will be beneficial to application?


On Tue, May 19, 2015 at 12:14 PM, Bland, Wesley <wesley.bland at intel.com>

> I plan to go over this during the con call next week, but if you’d like to
> get a preview and/or comment early, I have a draft of the slides for the
> reading for ticket #324. You can view the slides here:
> https://docs.google.com/presentation/d/10Sz9aCDezSLH1rss6XYApo_wVqTyHH08G3FUe9NcygE/edit?usp=sharing
> If you have any questions/comments, let me know.
> Aurelien, I’m not sure of the status of this ticket in Open MPI. Is there
> a way to keep Open MPI from aborting on any error in the trunk? Is the only
> way to get this in the ULFM repo?
> Thanks,
> Wesley
> _______________________________________________
> mpiwg-ft mailing list
> mpiwg-ft at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-ft/attachments/20150520/1e9a3526/attachment-0001.html>

More information about the mpiwg-ft mailing list