Performance, Safety and Idioms in Parallel Programming Systems (1995)
BibTeX
@MISC{Lu95performance,safety,
author = {Paul Lu},
title = {Performance, Safety and Idioms in Parallel Programming Systems},
year = {1995}
}
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
ions are too low level. Many PPSs are designed around specific mechanisms, instead of around problem-solving techniques. The programmer is responsible for correctness and performance tuning. The need for higher levels of abstraction is well known, but low-level PPSs continue to dominate the literature. One important exception is the work on data-parallel languages, such as High Performance Fortran (HPF) [KLS+94]. However, HPF only supports one paradigm for parallel programming, so it will not be examined in this survey of more general-purpose systems. 2. Interfaces are too low level. Sometimes, the abstractions are fairly high level (e.g., shared data on multicomputers), but the interface to the abstraction is too low level (e.g., load-store operations). With a low-level interface, it is more difficult for the PPS to transparently change the abstraction's implementation to use more efficient mechanisms and policies. Some researchers have argued for high-level interfaces [LKB+92], but t...
