<div dir="ltr">Got it, thanks guys.<div><br></div><div> ~Jim.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 22, 2013 at 3:15 PM, Wesley Bland <span dir="ltr"><<a href="mailto:wbland@mcs.anl.gov" target="_blank">wbland@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>No, it's a correctness thing. You're only required to detect failures for processes you're actively communicating with (in a collective, receiving/sending a message). If you're not directly communicating, the implementation isn't required to notify you of a failure (and it would be confusing if it did). In this case, you might need the revoke to notify the other processes manually an example might be a stencil computation where nor process detects a failure and decides to branch to a recovery path. You might need to revoke the communicator first before branching. </div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Wesley</div></font></span><div><div class="h5"><div><br>On Nov 22, 2013, at 2:02 PM, Jim Dinan <<a href="mailto:james.dinan@gmail.com" target="_blank">james.dinan@gmail.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">So, what is the argument for having MPI_Comm/win_revoke? Is it a performance, rather than a correctness argument?<div><br></div><div> ~Jim.</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Fri, Nov 22, 2013 at 2:01 PM, Wesley Bland <span dir="ltr"><<a href="mailto:wbland@mcs.anl.gov" target="_blank">wbland@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>It doesn't require an asynchronous failure detector. It does require that you detect failures (in a unspecified way) insofar as it prevents completion. Once you enter the MPI library, you have to use some sort of detector (probably from the runtime level) to keep from getting deadlocked. </div>
<span><font color="#888888"><div><br></div><div>Wesley</div></font></span><div><div><div><br>On Nov 22, 2013, at 12:53 PM, Jim Dinan <<a href="mailto:james.dinan@gmail.com" target="_blank">james.dinan@gmail.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">The latter case requires a failure detector, right? I had thought the current design would avoid this requirement.<div><br></div><div> ~Jim.</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Thu, Nov 21, 2013 at 12:06 PM, Wesley Bland <span dir="ltr"><<a href="mailto:wbland@mcs.anl.gov" target="_blank">wbland@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>No problem about missing the call yesterday. It was a last minute thing. I think we're in good shape to submit the text on Monday, but we're just doing some final passes over the text. There were a few changes that Aurélien will be making and I'm getting Gail to do an English pass, but overall, it's still essentially the same as what we read last year (per the request from the forum).</div>
<div><br></div><div>There are a couple of ways out of this deadlock. The first is, as you mentioned, to have a function in the library to essentially manually trigger an error handler and let the library figure out what is wrong. This method would work, but it is a bit heavy handed. The alternative solution is that the wildcard on process X should return an error because the failure of process Y meets the definition if an "involved process." Process X will get an exception (or an MPI_Errhandler) and can trigger the recovery path. </div>
<div><br></div><div>Either way should work, but the later is obviously the preferred and expected solution. </div><div><br></div><div>Thanks,</div><div>Wesley</div><div><div><div><br>On Nov 21, 2013, at 10:58 AM, Jim Dinan <<a href="mailto:james.dinan@gmail.com" target="_blank">james.dinan@gmail.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">Hi Guys,<div><br></div><div>Sorry I wasn't able to attend. I'm back from SC now, if you need me.</div><div><br></div><div>I have a concern about the current approach to revoking communicators. Consider a program that uses a library with a communicator, CL, that is private to the library. Process X makes a call to this library and performs a wildcard receive on CL. Process Y fails; Y would have sent a message to X on CL. Process Z sees that Y failed, but it sees it in the user code, outside of the library. Process Z cannot call revoke on CL because it does not have any knowledge about how the library is implemented and it does not have a handle to CL.</div>
<div><br></div><div>This seems like a situation that will result in deadlock, unless the library is also extended to include a "respond to process failure" function. Is this handled in some other way, and I'm just not seeing it?</div>
<div><br></div><div>It seems like the revoke(comm) approach requires the programmer to know about all communication and all communicators/windows in use in their entire application, including those contained within libraries. Is that a correct assessment?</div>
<div><br></div><div> ~Jim.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 20, 2013 at 2:39 PM, Aurélien Bouteiller <span dir="ltr"><<a href="mailto:bouteill@icl.utk.edu" target="_blank">bouteill@icl.utk.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Rich, this is a followup of the proofreading work done during the regular meeting we had last week, and everybody, including SC attendees, had a chance to join. I am sorry you couldn’t.<br>
<br>
Anyway, here is the working document for today: all diffs since the introduction of the new RMA chapter 5 month ago.<br>
<br>
<br>
<br><br>
<br>
<br>
<br>
<br>
Le 19 nov. 2013 ŕ 17:07, Richard Graham <<a href="mailto:richardg@mellanox.com" target="_blank">richardg@mellanox.com</a>> a écrit :<br>
<br>
> With SC this week this is poor timing<br>
><br>
> Rich<br>
><br>
> ------Original Message------<br>
> From: Wesley Bland<br>
> To: MPI WG Fault Tolerance and Dynamic Process Control working Group<br>
> Cc: MPI WG Fault Tolerance and Dynamic Process Control working Group<br>
> ReplyTo: MPI WG Fault Tolerance and Dynamic Process Control working Group<br>
> Subject: Re: [mpiwg-ft] A meeting this week<br>
> Sent: Nov 19, 2013 2:13 PM<br>
><br>
> Ok. I'll be there. I'll send it off for an editing today.<br>
><br>
> Wesley<br>
><br>
>> On Nov 19, 2013, at 3:12 PM, Aurélien Bouteiller <<a href="mailto:bouteill@icl.utk.edu" target="_blank">bouteill@icl.utk.edu</a>> wrote:<br>
>><br>
>> Dear WG members,<br>
>><br>
>> We have been misreading the new forum rules. We have to buckle the text of the proposal this week and not in 2 weeks from now, so time is running short. I would like to invite you to a supplementary meeting tomorrow to make a review of the text together.<br>
>><br>
>> Jim, I don’t know if you will be able to attend on short notice, but your input would be greatly appreciated.<br>
>><br>
>> Date: Wed, November 20,<br>
>> Time: 3pm EDT/New York<br>
>> Dial-in information: <a href="tel:712-432-0360" value="+17124320360" target="_blank">712-432-0360</a><br>
>> Code: 623998#<br>
>><br>
>> Agenda:<br>
>> Review of ULFM text and final work.<br>
>><br>
>> Aurelien<br>
>><br>
>> --<br>
>> * Dr. Aurélien Bouteiller<br>
>> * Researcher at Innovative Computing Laboratory<br>
>> * University of Tennessee<br>
>> * 1122 Volunteer Boulevard, suite 309b<br>
>> * Knoxville, TN 37996<br>
>> * <a href="tel:865%20974%209375" value="+18659749375" target="_blank">865 974 9375</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> mpiwg-ft mailing list<br>
>> <a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a><br>
>> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br>
> _______________________________________________<br>
> mpiwg-ft mailing list<br>
> <a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a><br>
> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br>
> _______________________________________________<br>
> mpiwg-ft mailing list<br>
> <a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a><br>
> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br>
<br>
--<br>
* Dr. Aurélien Bouteiller<br>
* Researcher at Innovative Computing Laboratory<br>
* University of Tennessee<br>
* 1122 Volunteer Boulevard, suite 309b<br>
* Knoxville, TN 37996<br>
* <a href="tel:865%20974%209375" value="+18659749375" target="_blank">865 974 9375</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>_______________________________________________<br>
mpiwg-ft mailing list<br>
<a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>mpiwg-ft mailing list</span><br><span><a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a></span><br>
<span><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a></span></div></blockquote></div></div></div><br>_______________________________________________<br>
mpiwg-ft mailing list<br>
<a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>mpiwg-ft mailing list</span><br><span><a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a></span><br>
<span><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a></span></div></blockquote></div></div></div><br>_______________________________________________<br>
mpiwg-ft mailing list<br>
<a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>mpiwg-ft mailing list</span><br><span><a href="mailto:mpiwg-ft@lists.mpi-forum.org" target="_blank">mpiwg-ft@lists.mpi-forum.org</a></span><br>
<span><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a></span></div></blockquote></div></div></div><br>_______________________________________________<br>
mpiwg-ft mailing list<br>
<a href="mailto:mpiwg-ft@lists.mpi-forum.org">mpiwg-ft@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-ft</a><br></blockquote></div><br></div>