<!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.3314" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>Dear Dick,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>A couple of suggestions re your
proposal:</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>- If ASSERTIONS is put at the end of the
MPI_INIT_ASSERTED argument list, in C++ one can declare the last argument as
having a <SPAN class=120465606-20062008>zero </SPAN>default value, and skip
it if necessary. This might help with deprecation of the earlier MPI_INIT_*
calls.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=799304706-20062008><FONT face=Arial><FONT
color=#0000ff><FONT size=2>- In non-Cray parts of the world, an MPI_INT followed
by MPI_FLOAT is likely to be a 4-byte int followed by a 4-byte float.<SPAN
class=120465606-20062008> This sometimes depends on the compiler settings in
effect, too.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>- I don't think MPI_NO_THREAD_CONTENTION is really
necessary. The original thread <SPAN class=120465606-20062008>level
</SPAN>settings, in particular, the use of anything but
MPI_THREAD_MULTIPLE, seem to capture the semantics that you
proposed.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>- I can't fully follow the motivation for
MPI_NO_ANY_SOURCE deprioritization. AFAIK, a rendezvous exchange usually starts
with a ready-to-send packet that contains the size of the message. In this
case the receiving side will normally reply with a ready-to-receive
regardless of the buffer space available, and flag MPI_ERR_TRUNCATED on message
arrival if necessary. In this case,<SPAN class=120465606-20062008> neither
MPI_ANY_SOURCE not </SPAN>MPI_NO_ANY_SOURCE seem to get into
way.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>Best regards.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008>Alexander</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=799304706-20062008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Supalov, Alexander <BR><B>Sent:</B>
Friday, June 20, 2008 8:29 AM<BR><B>To:</B> 'MPI 3.0 Sub-setting working
group'<BR><B>Subject:</B> RE: [Mpi3-subsetting] MPI subsetting: charting the way
forward at atelecon next week?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2>Dear Dick,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2>Thank you. I remember we exchanged a couple of emails about
the possible extensions to the set of assertions, like one-sided and I/O, and in
my recollection, almost reached an agreement that this can improve performance
and possibly memory footprint, as well as be expressed thru assertions. Do you
still feel favorable about this?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2>Best regards.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=778272606-20062008><FONT face=Arial
color=#0000ff size=2>Alexander</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-subsetting-bounces@lists.mpi-forum.org
[mailto:mpi3-subsetting-bounces@lists.mpi-forum.org] <B>On Behalf Of </B>Richard
Treumann<BR><B>Sent:</B> Thursday, June 19, 2008 9:01 PM<BR><B>To:</B> MPI 3.0
Sub-setting working group<BR><B>Subject:</B> Re: [Mpi3-subsetting] MPI
subsetting: charting the way forward at atelecon next week?<BR></FONT><BR></DIV>
<DIV></DIV>
<P>Hello to the Subset WG<BR><BR>I appreciate the interest in my proposal for
Init time assertions. Unfortunately I will not be able to come to the next Forum
meeting to discuss face to face.<BR><BR>I did write up a fairly detailed draft a
few weeks back and post it on the MPI 2.2 Wiki at: <A
href="http://svn.mpi-forum.org/trac/mpi-forum-web/wiki/InitTimeAssertions">http://svn.mpi-forum.org/trac/mpi-forum-web/wiki/InitTimeAssertions</A><BR><BR>Maybe
that will help clarify what I have in mind. My proposal does not include "hints"
so I did not discuss the definition of a hint. I did try to be firm about the
meaning of an assertion.<BR><BR>Dick Treumann<BR><BR>Dick Treumann - MPI
Team/TCEM <BR>IBM Systems & Technology Group<BR>Dept 0lva / MS P963 -- 2455
South Road -- Poughkeepsie, NY 12601<BR>Tele (845) 433-7846 Fax (845)
433-8363<BR></P><pre>---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
</pre></BODY></HTML>