<!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.3243" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>Hi
everybody,</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>In the
run-up to our kick-off, here's my POV on the subsetting and its possible
scope/role in the MPI-3. <SPAN class=593012610-26022008><FONT face=Arial
color=#0000ff size=2>Your comments and suggestions are most
welcome.</FONT></SPAN>
<DIV><SPAN class=593012610-26022008></SPAN></FONT></SPAN><SPAN
class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>We
start this activity because:</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>1)
Certain industrial customers complain about MPI complexity and
inadequacy</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>2)
Complexity is going to grow in MPI-3</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>3)
Growing complexity may have growing performance
implications</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>As a
result of the above, customers drift away from the MPI to home-grown libraries,
usually based on sockets. This effectively eliminates fast networks from their
scope, unless they can profit from fast IP emulation layers.
Moreover, this c</FONT></SPAN><SPAN class=593012610-26022008><FONT face=Arial
color=#0000ff size=2>ustomer drift, if continued, may make MPI irrelevant in
some HPC areas and lead to creation of alternative interfaces
there.</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>The
main purpose of the Forum, as well as the subsetting WG, is thus to react to
customer demand and make MPI faster and easier to use, especially in those
areas that are subjected to the increasing customer drift (think,
e.g., massive master-slave computations).</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>Basing
on these premises, the subsetting, in my mind, should try
to:</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>1)
Make MPI standard modular. This may include:</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008> <FONT face=Arial
color=#0000ff size=2>a) Splitting the standard functionality into coherent
groups that users will be able to select/deselect at init
time</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008> <FONT face=Arial
color=#0000ff size=2>b) Making implementation of some modules/functionality
optional (think dynamic process support) as they are anyway
now</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008> <FONT face=Arial
color=#0000ff size=2>c) Addressing not only functional groups but also certain
aspects of the standard that may not be needed in certain use cases (think
communicator management, message tagging, derived datatypes, MPI_ANY_SOURCE
support, non-blocking communication, etc.)</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>2) As
part of the modularization, optionally identify the minimum functional MPI
subset. This may be:</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008> <FONT face=Arial
color=#0000ff size=2>a) Those 6 calls (Init, Rank, Size, Send, Recv, Finalize),
possibly w/o communicator management and derived datatypes.</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008> <FONT face=Arial
color=#0000ff size=2>b) A more flexible combination of modules actually needed
by the user</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>3)
Connect subsetting with other MPI-3 activities (FT, ABI, collectives,
etc.)</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>As a
result of modularization, we should strive to achieve</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial><FONT color=#0000ff
size=2></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial><FONT color=#0000ff
size=2>1) Simplification of the standard for the
newcomers</FONT></FONT></SPAN></DIV>
<DIV><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN
class=593012610-26022008>2</SPAN><SPAN class=593012610-26022008>) Performance
advantages for reasonable module
combinations</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>3)
Influence upon the overall shape of the MPI-3 standard</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>There
are certainly quite a few concerns here:</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>1) We
may end up complicating the standard and its implementation even
further</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>2) We
may facilitate a split of the standard into several mutually incompatible
implementation "families"</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>3) We
may cause some valid MPI-3 applications break if they use optional modules not
available in the implementation involved</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>4) We
may get carried away by academic considerations and miss the actual customer
demands in the process</FONT></SPAN></DIV><FONT face=Arial><FONT
color=#0000ff><FONT size=2><SPAN class=593012610-26022008>5</SPAN>) We
may be engaging into a lost battle because the MPI standard is
way too rigid by design/purpose to be
simplified</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>To
guard against all this, we need to work closely with other WGs and the
Forum as a whole, define our goals as early as possible, and solicit extensive
Forum and customer feedback.</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>From
all this, by the time of the Forum meeting in March, we should have at least a
couple of slides reflecting our intentions and
plans.</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff size=2>Best
regards.</FONT></SPAN></DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=593012610-26022008><FONT face=Arial color=#0000ff
size=2>Alexander</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV align=left><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">
<DIV dir=ltr align=left><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">--</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
class=SpellE><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">Dr</SPAN></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">
Alexander Supalov</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">Intel
GmbH</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
class=SpellE><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">Hermuelheimer</SPAN></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">
Strasse 8a</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">50321
<SPAN class=SpellE>Bruehl</SPAN>, Germany</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">Phone: +49
2232 209034</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">Mobile:
+49<I> </I>173 511 8735</SPAN></DIV>
<DIV><SPAN lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE"></SPAN><SPAN
lang=DE
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: DE">Fax: <SPAN
style="mso-spacerun: yes"> </SPAN>+49 2232 209029</SPAN></DIV></SPAN></DIV>
<DIV> </DIV></BODY></HTML>