Skip to main navigation Skip to search Skip to main content

High performance checksum computation for fault-tolerant MPI over infiniband

  • INRIA Institut National de Recherche en Informatique et en Automatique
  • CNRS SAMOVAR UMR 5157
  • University of Tokyo

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

With the increase of the number of nodes in clusters, the probability of failures and unusual events increases. In this paper, we present checksum mechanisms to detect data corruption. We study the impact of checksums on network communication performance and we propose a mechanism to amortize their cost on InfiniBand. We have implemented our mechanisms in the NewMadeleine communication library. Our evaluation shows that our mechanisms to ensure message integrity do not impact noticeably the application performance, which is an improvement over the state of the art MPI implementations.

Original languageEnglish
Title of host publicationRecent Advances in the Message Passing Interface - 19th European MPI Users' Group Meeting, EuroMPI 2012, Proceedings
Pages183-192
Number of pages10
DOIs
Publication statusPublished - 24 Oct 2012
Externally publishedYes
Event19th European MPI Users' Group Meeting on Recent Advances in the Message Passing Interface, EuroMPI 2012 - Vienna, Austria
Duration: 23 Sept 201226 Sept 2012

Publication series

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

Conference

Conference19th European MPI Users' Group Meeting on Recent Advances in the Message Passing Interface, EuroMPI 2012
Country/TerritoryAustria
CityVienna
Period23/09/1226/09/12

Keywords

  • Checksum
  • Fault-Tolerance
  • High-performance networks
  • InfiniBand

Fingerprint

Dive into the research topics of 'High performance checksum computation for fault-tolerant MPI over infiniband'. Together they form a unique fingerprint.

Cite this