90 likes | 111 Views
Open MPI Progress. Jeff Squyres. Academia / Research HLRS Indiana University Sandia National Laboratory Los Alamos National Laboratory University of Dresden University of Houston University of Tennessee. Industry Cisco IBM Mellanox Myricom QLogic Sun Voltaire. Community members.
E N D
Open MPI Progress Jeff Squyres
Academia / Research HLRS Indiana University Sandia National Laboratory Los Alamos National Laboratory University of Dresden University of Houston University of Tennessee Industry Cisco IBM Mellanox Myricom QLogic Sun Voltaire Community members
Academic / research involvement • Driving the project • Ability to influence the project in research-driven directions • Directly contribute code / engineering time • Provide access to large testing clusters • Bleeding edge research • New approaches, new ideas • Pursue directions that vendors do not have resources to • Publish results • Feeds directly into vendor product lines • [Dramatically] Shorten the time between research and product
Vendor involvement • Driving the project • Ability to influence the project in customer-driven directions • Directly contribute code / engineering time • Vendors provide large influx of QA resources • Lots of vendor-specific tests • v1.2 contains lots of little fixes as a result • Maintain in-house expertise to support customers
Current status • v1.1.2 is current stable • v1.1.3 expected “soon” (bug fix release) • v1.2 expected Q1’07 • All IB vendors involved in development and testing • No real need to discuss specific features here • Emphasis on scalability, stability, reliability, repeatability • Reflects strong vendor involvement • Hopefully in time for OFED 1.2
Distributed automated testing • Nightly regression testing at member sites • Automated testing harness • Developed and maintained by Cisco, Sun, Indiana University • Centralized tracking of all results • Tremendous improvement in quality • Release managers rely on this data
MPI wish list • Biggest item: cheap memory register / deregister • Get true hardware-provided overlap • Avoid complicated pipeline protocol • Memory hooks • If memory registration is cheap enough, moot point • Memory re-register without de-register • Done in ibverbs 1.1