Advanced Search

Journal Navigation

Journal Home

Subscriptions

Archive

Contact Us

Table of Contents

Click here to sign up for SAGE Journal Email Alerts today!

Sign In to gain access to subscriptions and/or personal tools.
International Journal of High Performance Computing Applications
This Article
Right arrow Full Text (PDF)
Right arrow All Versions of this Article:
1094342009347768v1
23/4/389    most recent
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Alert me to new issues of the journal
Right arrow Add to Saved Citations
Right arrow Download to citation manager
Right arrowRequest Permissions
Right arrow Request Reprints
Right arrow Add to My Marked Citations
Citing Articles
Right arrow Citing Articles via Scopus
Google Scholar
Right arrow Articles by Kramer, W.
Right arrow Articles by Skinner, D.
Social Bookmarking
Add to CiteULike   Add to Complore   Add to Connotea   Add to Del.icio.us   Add to Digg   Add to Reddit   Add to Technorati   Add to Twitter  
What's this?

An Exascale Approach to Software and Hardware Design

William Kramer

NERSC; LAWRENCE BERKELEY NATIONAL LABORATORY, NATIONAL ENERGY RESEARCH SUPERCOMP, USA, WKRAMER{at}NCSA.UIUC.EDU

David Skinner

NERSC; LAWRENCE BERKELEY NATIONAL LABORATORY, NATIONAL ENERGY RESEARCH SUPERCOMP, USA

For the past 10—15 years, horizontal layers of software and hardware design and development have been the de facto standard of creating high-performance computing (HPC) software. The horizontal design approach leads to the development of discrete components in the software stack and independent hardware components — all developed with different methods, requirements and quality dominated by plug-and-play componentization that is focused on horizontal functionality and portability. The horizontal software paradigm will break down at the exascale due to the system scale and complexity. The vertical approach needed for the exascale should include resilience (reliability and fault tolerance); performance; programmability; computational models; I/O; consistency and verification; resource management; and power management/total cost of ownership. To make the exascale an effective reality, instead of thinking of integration as the final step in defining and developing an exascale system, it will have to be the first step.

Key Words: software design • operating systems • performance measurement • resiliency • I/O

This version was published on November 1, 2009

International Journal of High Performance Computing Applications, Vol. 23, No. 4, 389-391 (2009)
DOI: 10.1177/1094342009347768
Add to CiteULike CiteULike   Add to Complore Complore   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us   Add to Digg Digg   Add to Reddit Reddit   Add to Technorati Technorati   Add to Twitter Twitter    What's this?