HPX - High Performance ParalleX

PrevUpHomeNext

Preface

History

The development of High Performance ParalleX (HPX) started back in 2007. At that point, Hartmut Kaiser became interested in the work done by the ParalleX group at the Center for Computation and Technology (CCT), a multi-disciplinary research institute at Louisiana State University (LSU). The ParalleX group was developing a new and experimental execution model for future high performance computing architectures called ParalleX. The first implementations were crude at best, and we had to dismiss those designs entirely. However, over time we learned quite a bit about how to design a parallel runtime system which implements the ideas of ParalleX.

Our goal is to create a high quality, freely available, open source implementation of the ParalleX model for conventional systems, such as classic Linux based Beowulf clusters or multi-socket highly parallel SMP nodes. At the same time, we want to have a very modular and well designed runtime system architecture which would allow us to port our implementation onto new computer system architectures. We want to use real world applications to drive the development of the runtime system, coining out required functionalities and converging onto an stable API which will provide a smooth migration path for developers.

From the very beginning, this endeavour has been a group effort. In addition to a handful of interested researchers, there have always been undergraduate and graduate students participating in the discussions, design, and implementation of HPX. In 2011 we decide to formalize our collective research efforts by creating the STE||AR group. STE||AR stands for Systems Technologies, Emergent Parallelism, and Algorithms Research, which describes the three main focal points we center our work around.

To learn more about STE||AR and ParalleX, see People and Introduction.

How to use this manual

Some icons are used to mark certain topics indicative of their relevance. These icons precede some text to indicate:

Table 1. Icons

Icon

Name

Meaning

note

Note

Generally useful information (an aside that doesn't fit in the flow of the text)

tip

Tip

Suggestion on how to do something (especially something that is not obvious)

important

Important

Important note on something to take particular notice of

caution

Caution

Take special care with this - it may not be what you expect and may cause bad results

alert

Danger

This is likely to cause serious trouble if ignored


The following table describes the syntax that will be used to refer to functions and classes throughout the manual:

Table 2. Syntax for Code References

Syntax

Meaning

foo()

The function foo

foo<>()

The template function foo (used only for template functions that require explicit parameters)

foo

The class foo

foo<>

The template class foo


Support

Please feel free to direct questions to HPX's mailing list: gopx@cct.lsu.edu or log onto our IRC channel which can be found at #stellar at Freenet.


PrevUpHomeNext