|
| The design of GASNet is partitioned into two layers to maximize porting ease without sacrificing performance: the lower level is a narrow but very general interface called the GASNet core API - the design is based heavily on Active Messages, and is implemented directly on top of each individual network architecture. The upper level is a wider and more expressive interface called the GASNet extended API, which provides high-level operations such as remote memory access and various collective operations. |
|
Most clients will use calls to the extended API functions to implement the bulk of their communication work (thereby ensuring optimal performance across platforms). However the client is also permitted to use the core active message interface to implement non-trivial language-specific or compiler-specific communication operations which would not be appropriate in a language-independent API (e.g. implementing distributed language-level locks, distributed garbage collection, collective memory allocation, etc.). The AM features of the core provide a powerful extensibility mechanism which allows clients to implement a wide variety of specialized communication operations.
For citations, please use:
|
GASNet Full Source Release (all conduits and platforms) |
GASNet-1.10.0.tar.gz (2 MB) MD5 Hash = 17eee04a24aa0b00135ea95592ebfac0 Browse the archive README, Change log, BSD license. |
|
GASNet Portability Tools (NO communication conduits, GASNet Tools only) |
GASNet_Tools-1.10.0.tar.gz (400 KB) MD5 Hash = b9b219369feb67f9230e0d284e14fd4e README-tools |
The full version of GASNet includes support for the following networks:
and has been tested on a number of systems (see README for a complete list):
Work continues on GASNet implementations for other high-performance networks, and code contributions are appreciated (please send email if you're interested). Future releases will add a further-tuned collectives implementation, native support for BlueGene systems, and numerous other improvements to the existing native conduits. Independent implementations of the GASNet specification are also encouraged.
UPC Language Consortium
Active Messages over MPI (AMMPI)
Active Messages over Ethernet/UDP (AMUDP)
ARMCI Communication System
For more info about GASNet, please contact:
Dan Bonachea
|
Page last updated Thursday November 08, 2007 |
|