<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=379551420-23102008><FONT face=Arial
color=#0000ff size=2>If the application "ensures" that there are no messages
in-flight, then I agree with you. I was thinking of applications that use
asyncronous MPI communication in a multi-threaded env, potentially leading to
unmatched messages..... </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=379551420-23102008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=379551420-23102008><FONT face=Arial
color=#0000ff size=2>-Kannan-</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mpi3-ft-bounces@lists.mpi-forum.org
[mailto:mpi3-ft-bounces@lists.mpi-forum.org] <B>On Behalf Of </B>Greg
Bronevetsky<BR><B>Sent:</B> Thursday, October 23, 2008 2:59 PM<BR><B>To:</B> MPI
3.0 Fault Tolerance and Dynamic Process Control working Group; MPI 3.0 Fault
Tolerance and Dynamic Process Control working Group<BR><B>Subject:</B> Re:
[Mpi3-ft] Summary of today's meeting<BR></FONT><BR></DIV>
<DIV></DIV>
<BLOCKQUOTE class=cite cite="" type="cite">
<UL><FONT color=#0000ff size=2>Application-directed C/R will still require
some quiescence hooks from the MPI layer (ex: asyncronous progression by the
MPI layer). There was some discussion on this.</FONT></UL></BLOCKQUOTE>
<UL></UL>What kind of quiscence are you thinking of? It seems to me that
applications will simply need to ensure that either no messages are in-flight at
the time of the checkpoint or that all such messages have been logged
appropriately by the application.<BR><X-SIGSEP>
<P></X-SIGSEP>Greg Bronevetsky<BR>Post-Doctoral Researcher<BR>1028 Building
451<BR>Lawrence Livermore National Lab<BR>(925)
424-5756<BR>bronevetsky1@llnl.gov </P></BODY></HTML>