<!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.3354" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008>Dear Jeff,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008>Thanks for the reminder. We did not do anything
special on Linux. Intel MPI is (almost) compliant with the proposed ABI by
definition, give or take a constant or two. OpenMPI team said they had no
resources to support this activity. I did not hear from anyone else on this
matter so far.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008>Best regards.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial size=2><SPAN
class=120020501-12122008>Alexander</SPAN></FONT></DIV><FONT face=Arial
size=2></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mpi3-abi-bounces@lists.mpi-forum.org
[mailto:mpi3-abi-bounces@lists.mpi-forum.org] <B>On Behalf Of </B>Jeff
Brown<BR><B>Sent:</B> Thursday, December 11, 2008 6:21 PM<BR><B>To:</B> MPI 3.0
ABI working group<BR><B>Cc:</B> craig Rasmussen; ddd@lanl.gov; Ralph
Castain<BR><B>Subject:</B> Re: [Mpi3-abi] Open MPI and ABI<BR></FONT><BR></DIV>
<DIV></DIV>All,<BR><BR>At the last meeting I attended (Dublin) we discussed
developing a prototype "morph" ABI layer with initial implementation targeting
the December meeting. Let's take stock of this effort when we meet next
week. As I recall, Ezra offered to lead the windows implementation, and
Alexander linux. This exercise is meant to expose some of the
implementation details and help drive us toward a detailed standard proposal we
can take to the larger group.<BR><BR>Ezra and Alexander, please brief us on this
effort when we meet next Wednesday.<BR><BR>From the Dublin meeting:<BR>•MPI ABI
standard, separate from MPI API standard, but under the umbrella of the MPI
Forum<BR>•Dynamic link is the main objective (binary compatibility)<BR>•Startup
(mpirun/mpiexec) is a secondary objective<BR>•Include all major language
bindings in the ABI standard (C, C++, Fortran) as we go<BR>•Tied to MPI 2.1 and
forward<BR>•Implementers may choose to comply (or not)<BR>•May be implemented as
a morph layer or native<BR>•Initial reference implementation will be a morph
layer (tbd who provides)<BR>•May be different per platform (Linux, Windows,
…)<BR>•Different voting rules separate from MPI API forum (?)<BR>•Need
participation from major implementors in order to make progress<BR><BR>mpi.h:
MPICH 2 (1.0.7) as base with mods as needed (e.g. max values for compile time
values used in declarations)<BR>Proceed with a reference morph layer
implementation targeting (at least) MPICH 2.0, OpenMPI <BR>Load a different
module and it just works<BR>Demonstrate with a ring program<BR>Defer startup
consideration<BR><BR>Proof of concept reference morph layer
implementations:<BR>•Flesh out details by writing some code<BR>•Linux on X86-64
cluster Red Hat Linux/SUSE<BR>•Windows on X86-64 cluster<BR>•Test against ring
program<BR>•<B>Bring back to the December forum meeting<BR><BR></B>see ya next
week<BR><BR>Jeff <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>