Open issues in MPI implementation

Rajeev Thakur, William Gropp

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

MPI (the Message Passing Interface) continues to be the dominant programming model for parallel machines of all sizes, from small Linux clusters to the largest parallel supercomputers such as IBM Blue Gene/L and Cray XT3. Although the MPI standard was released more than 10 years ago and a number of implementations of MPI are available from both vendors and research groups, MPI implementations still need improvement in many areas. In this paper, we discuss several such areas, including performance, scalability, fault tolerance, support for debugging and verification, topology awareness, collective communication, derived datatypes, and parallel I/O. We also present results from experiments with several MPI implementations (MPICH2, Open MPI, Sun, IBM) on a number of platforms (Linux clusters, Sun and IBM SMPs) that demonstrate the need for performance improvement in one-sided communication and support for multithreaded programs.

Original languageEnglish (US)
Title of host publicationAdvances in Computer Systems Architecture - 12th Asia-Pacific Conference, ACSAC 2007, Proceedings
PublisherSpringer
Pages327-338
Number of pages12
ISBN (Print)9783540743088
DOIs
StatePublished - 2007
Externally publishedYes
Event12th Asia-Pacific Computer Systems Architecture Conference, ACSAC 2007 - Seoul, Korea, Republic of
Duration: Aug 23 2007Aug 25 2007

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume4697 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Other

Other12th Asia-Pacific Computer Systems Architecture Conference, ACSAC 2007
Country/TerritoryKorea, Republic of
CitySeoul
Period8/23/078/25/07

ASJC Scopus subject areas

  • Theoretical Computer Science
  • General Computer Science

Fingerprint

Dive into the research topics of 'Open issues in MPI implementation'. Together they form a unique fingerprint.

Cite this