Howard Pritchard

Howard Pritchard

Auto-generated profile, based on publicly available information

Howard Pritchard

Los Alamos National Laboratory

Research Focus & Metrics

Academic Career Length

10Years (2017-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 January 2022
Verified
Book Chapter
Closed access
PDF file
JFJan Fecht
Jan Fecht
MSMartin Schreiber
Martin Schreiber
MSMartin Schulz
Martin Schulz
HPHoward Pritchard
Howard Pritchard
DHDaniel J. Holmes
Daniel J. Holmes

23 July 2024 in The International Journal of High Performance Computing Applications
Verified
Journal Article
Closed access
DBDavid E Bernholdt
David E Bernholdt
GBGeorge Bosilca
George Bosilca
ABAurelien Bouteiller
Aurelien Bouteiller
RBRon Brightwell
Ron Brightwell
JCJan Ciesko
Jan Ciesko
ASAmir Shehata
Amir Shehata
The Open MPI for Exascale (OMPI-X) project was one of two in the Exascale Computing Project (ECP) focused on advancing the MPI ecosystem. The OMPI-X team worked with other MPI Forum members to champion several important features for inclusion in the MPI 4.0, 4.1, and upcoming 5.0 MPI standard versions, in support of the needs of exascale applications and systems. The team also worked with the larger Open MPI community to bring implementations of these new features and other enhancements into Open MPI, one of the leading open-source implementations of the MPI interface. This paper describes the motivation for the work of the OMPI-X project in the context of exascale computing needs, the nature of the resulting new capabilities in the MPI standard, and how they were implemented in the Open MPI library. Features include improved support for “MPI + X” programming models through partitioned communications and support for user-level threading, sessions, fault tolerance through the user-level fault mitigation (ULFM) and Reinit models, and other features. We also discuss enhancements to Open MPI providing improved performance and scalability for existing features, such as collective operations, one-sided operations, support for the Slingshot-11 interconnect of the initial exascale systems, and how the OMPI-X team worked to improve quality assurance for the Open MPI library, particularly on platforms of interest to the Department of Energy community.

1 December 2017
Verified
Report
Open access
PDF file
MBMatthew B. Baker
Matthew B. Baker
SBSwen Boehm
Swen Boehm
ABAurelien Bouteiller
Aurelien Bouteiller
BCBarbara Chapman
Barbara Chapman
RCRobert Cernohous
Robert Cernohous
PSPavel Shamis
Pavel Shamis
The U.S. Department of Energy's Office of Scientific and Technical Information

18 July 2024 in Concurrency and Computation: Practice and Experience
Verified
Journal Article
Closed access
ASAmir Shehata
Amir Shehata
TNThomas Naughton
Thomas Naughton
DBDavid E. Bernholdt
David E. Bernholdt
HPHoward Pritchard
Howard Pritchard

11 September 2023
Verified
Conference Paper
Open access
JTJake Tronge
Jake Tronge
HPHoward Pritchard
Howard Pritchard
JBJed Brown
Jed Brown
A program or library is considered safe when it’s guaranteed that programmer error cannot cause undefined behavior. MPI, both the standard and its implementations, is not designed to be type or memory safe. The standard requires that types must match across point-to-point communications and that collective call arguments must be the same across all ranks; it is up to the user in most cases to avoid these errors, and if not caught, then program behavior is undefined. Existing research attempts to help application developers find these errors using profiling and debugging tools, but these do not focus on solving the problems of safety. These tools are usually designed to catch errors during development but safety errors can depend on the environment, hardware, and input values, thus they are likely to show up even during production runs. To properly bind and use MPI, many modern memory safe languages, such as Rust, have to carefully validate and check for these errors, making it hard to achieve the performance of languages like Fortran and C. Our work examines how to improve MPI safety, both type and memory safety, at the implementation level and within programming languages; in this way it is possible to ensure valid communication and safety whether in development or in production. Our work presents safe point-to-point messaging prototypes within an MPI implementation and as a UCX-based library written in the Rust programming language. These prototypes are both designed to catch point-to-point communication errors at runtime, specifically datatype mismatches. We analyze results from these prototypes to show that catching these types of errors can be done efficiently, both at the level of the language and the implementation.

12 November 2023
Verified
Conference Paper
Open access
JTJake Tronge
Jake Tronge
HPHoward Pritchard
Howard Pritchard
The Message-Passing Interface (MPI) requires implementations that are able to adapt to new hardware and architectures while ensuring correctness and usability. The most widely used MPI implementations, however, are written in older programming languages that can lead to memory-unsafe code with poor isolation between modules, and complicated interfaces that can lead to serious bugs, all of which leads to difficulty in testing, debugging, and checking for correctness. In order to improve development of MPI implementations, we posit that new components, and key existing code segments, may benefit from being written in the Rust programming language. In this work we reimplement a core component of Open MPI used for intra-node communication in Rust and show that it achieves performance approaching that of the existing, highly optimized, C code, demonstrating that Rust is able to provide performance while allowing for better testing, memory safety guarantees, and correctness.