From jeffb at [hidden] Thu Dec 11 11:20:47 2008 From: jeffb at [hidden] (Jeff Brown) Date: Thu, 11 Dec 2008 10:20:47 -0700 Subject: [Mpi3-abi] Open MPI and ABI In-Reply-To: <20080915170854.8A6421F8002@ccs-mail.lanl.gov> Message-ID: <20081211172050.03AF81F8004@ccs-mail.lanl.gov> All, 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. Ezra and Alexander, please brief us on this effort when we meet next Wednesday. From the Dublin meeting: •MPI ABI standard, separate from MPI API standard, but under the umbrella of the MPI Forum •Dynamic link is the main objective (binary compatibility) •Startup (mpirun/mpiexec) is a secondary objective •Include all major language bindings in the ABI standard (C, C++, Fortran) as we go •Tied to MPI 2.1 and forward •Implementers may choose to comply (or not) •May be implemented as a morph layer or native •Initial reference implementation will be a morph layer (tbd who provides) •May be different per platform (Linux, Windows, …) •Different voting rules separate from MPI API forum (?) •Need participation from major implementors in order to make progress mpi.h: MPICH 2 (1.0.7) as base with mods as needed (e.g. max values for compile time values used in declarations) Proceed with a reference morph layer implementation targeting (at least) MPICH 2.0, OpenMPI Load a different module and it just works Demonstrate with a ring program Defer startup consideration Proof of concept reference morph layer implementations: •Flesh out details by writing some code •Linux on X86-64 cluster Red Hat Linux/SUSE •Windows on X86-64 cluster •Test against ring program •Bring back to the December forum meeting ee ya next week Jeff * -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.supalov at [hidden] Thu Dec 11 20:09:01 2008 From: alexander.supalov at [hidden] (Supalov, Alexander) Date: Fri, 12 Dec 2008 02:09:01 +0000 Subject: [Mpi3-abi] Open MPI and ABI In-Reply-To: <20081211172050.03AF81F8004@ccs-mail.lanl.gov> Message-ID: <928CFBE8E7CB0040959E56B4EA41A77E0CB57B27@irsmsx504.ger.corp.intel.com> Dear Jeff, 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. Best regards. Alexander ________________________________ From: mpi3-abi-bounces_at_[hidden] [mailto:mpi3-abi-bounces_at_[hidden]] On Behalf Of Jeff Brown Sent: Thursday, December 11, 2008 6:21 PM To: MPI 3.0 ABI working group Cc: craig Rasmussen; ddd_at_[hidden]; Ralph Castain Subject: Re: [Mpi3-abi] Open MPI and ABI All, 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. Ezra and Alexander, please brief us on this effort when we meet next Wednesday. >From the Dublin meeting: *MPI ABI standard, separate from MPI API standard, but under the umbrella of the MPI Forum *Dynamic link is the main objective (binary compatibility) *Startup (mpirun/mpiexec) is a secondary objective *Include all major language bindings in the ABI standard (C, C++, Fortran) as we go *Tied to MPI 2.1 and forward *Implementers may choose to comply (or not) *May be implemented as a morph layer or native *Initial reference implementation will be a morph layer (tbd who provides) *May be different per platform (Linux, Windows, ...) *Different voting rules separate from MPI API forum (?) *Need participation from major implementors in order to make progress mpi.h: MPICH 2 (1.0.7) as base with mods as needed (e.g. max values for compile time values used in declarations) Proceed with a reference morph layer implementation targeting (at least) MPICH 2.0, OpenMPI Load a different module and it just works Demonstrate with a ring program Defer startup consideration Proof of concept reference morph layer implementations: *Flesh out details by writing some code *Linux on X86-64 cluster Red Hat Linux/SUSE *Windows on X86-64 cluster *Test against ring program *Bring back to the December forum meeting ee ya next week Jeff --------------------------------------------------------------------- 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. * -------------- next part -------------- An HTML attachment was scrubbed... URL: From erezh at [hidden] Fri Dec 12 10:55:37 2008 From: erezh at [hidden] (Erez Haba) Date: Fri, 12 Dec 2008 08:55:37 -0800 Subject: [Mpi3-abi] Open MPI and ABI In-Reply-To: <20081211172050.03AF81F8004@ccs-mail.lanl.gov> Message-ID: <6B68D01C00C9994A8E150183E62A119E7B5CB09573@NA-EXMSG-C105.redmond.corp.microsoft.com> I am sorry Jeff, there was no progress on my front wrt ABI. From: mpi3-abi-bounces_at_[hidden] [mailto:mpi3-abi-bounces_at_[hidden]] On Behalf Of Jeff Brown Sent: Thursday, December 11, 2008 9:21 AM To: MPI 3.0 ABI working group Cc: craig Rasmussen; ddd_at_[hidden]; Ralph Castain Subject: Re: [Mpi3-abi] Open MPI and ABI All, 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. Ezra and Alexander, please brief us on this effort when we meet next Wednesday. >From the Dublin meeting: *MPI ABI standard, separate from MPI API standard, but under the umbrella of the MPI Forum *Dynamic link is the main objective (binary compatibility) *Startup (mpirun/mpiexec) is a secondary objective *Include all major language bindings in the ABI standard (C, C++, Fortran) as we go *Tied to MPI 2.1 and forward *Implementers may choose to comply (or not) *May be implemented as a morph layer or native *Initial reference implementation will be a morph layer (tbd who provides) *May be different per platform (Linux, Windows, ...) *Different voting rules separate from MPI API forum (?) *Need participation from major implementors in order to make progress mpi.h: MPICH 2 (1.0.7) as base with mods as needed (e.g. max values for compile time values used in declarations) Proceed with a reference morph layer implementation targeting (at least) MPICH 2.0, OpenMPI Load a different module and it just works Demonstrate with a ring program Defer startup consideration Proof of concept reference morph layer implementations: *Flesh out details by writing some code *Linux on X86-64 cluster Red Hat Linux/SUSE *Windows on X86-64 cluster *Test against ring program *Bring back to the December forum meeting ee ya next week Jeff * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffb at [hidden] Fri Dec 12 11:00:22 2008 From: jeffb at [hidden] (Jeff Brown) Date: Fri, 12 Dec 2008 10:00:22 -0700 Subject: [Mpi3-abi] Open MPI and ABI In-Reply-To: <6B68D01C00C9994A8E150183E62A119E7B5CB09573@NA-EXMSG-C105.r edmond.corp.microsoft.com> Message-ID: <20081212170024.BB4A31F8003@ccs-mail.lanl.gov> ditto here (we are all busy) it may be a short meeting then! At 09:55 AM 12/12/2008, you wrote: >I am sorry Jeff, there was no progress on my front wrt ABI. > >From: mpi3-abi-bounces_at_[hidden] >[mailto:mpi3-abi-bounces_at_[hidden]] On Behalf Of Jeff Brown >Sent: Thursday, December 11, 2008 9:21 AM >To: MPI 3.0 ABI working group >Cc: craig Rasmussen; ddd_at_[hidden]; Ralph Castain >Subject: Re: [Mpi3-abi] Open MPI and ABI > >All, > >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. > >Ezra and Alexander, please brief us on this >effort when we meet next Wednesday. > > >From the Dublin meeting: >•MPI ABI standard, separate from MPI API >standard, but under the umbrella of the MPI Forum >•Dynamic link is the main objective (binary compatibility) >•Startup (mpirun/mpiexec) is a secondary objective >•Include all major language bindings in the ABI >standard (C, C++, Fortran) as we go >•Tied to MPI 2.1 and forward >•Implementers may choose to comply (or not) >•May be implemented as a morph layer or native >•Initial reference implementation will be a morph layer (tbd who provides) >•May be different per platform (Linux, Windows, …) >•Different voting rules separate from MPI API forum (?) >•Need participation from major implementors in order to make progress > >mpi.h: MPICH 2 (1.0.7) as base with mods as >needed (e.g. max values for compile time values used in declarations) >Proceed with a reference morph layer >implementation targeting (at least) MPICH 2.0, OpenMPI >Load a different module and it just works >Demonstrate with a ring program >Defer startup consideration > >Proof of concept reference morph layer implementations: >•Flesh out details by writing some code >•Linux on X86-64 cluster Red Hat Linux/SUSE >•Windows on X86-64 cluster >•Test against ring program >•Bring back to the December forum meeting > >see ya next week > >Jeff >_______________________________________________ >mpi3-abi mailing list >mpi3-abi_at_[hidden] >http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-abi * -------------- next part -------------- An HTML attachment was scrubbed... URL: