June 1st, 2020: Berkeley Lab is hiring!
The Computer Languages and System Software Group (CLaSS) in the Computing
Research Division (CRD) at Lawrence Berkeley National Laboratory (LBNL) is
recruiting for a Group Lead.
See job posting for more info.
GASNet is a language-independent, networking middleware layer that provides
network-independent, high-performance communication primitives including
Remote Memory Access (RMA) and Active Messages (AM).
It has been used to implement parallel programming models and libraries
such as UPC,
and many others.
The interface is primarily
intended as a compilation target and for use by runtime library writers (as
opposed to end users), and the primary goals are high performance, interface
portability, and expressiveness. GASNet stands for "Global-Address
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.
System diagram showing GASNet layers
We've written a network-independent reference implementation of the extended
API purely in terms of the core API, which allows GASNet (and its portable clients)
to quickly and easily be ported to a new network architecture by re-implementing
only the minimal core API. GASNet is structured such that implementers can
choose to additionally bypass certain functions in the reference implementation
of the extended API and implement them directly on the hardware to improve
performance of specific operations when hardware support is available (e.g.
RDMA support for puts/gets or hardware-offloaded atomic memory 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
GASNet-EX: A major specification upgrade and implementation renovation effort is currently in progress:
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 and numerous other improvements to the existing native conduits.
Independent implementations of the GASNet specification
are also encouraged.
Bug reports and Feature Requests :
Please do NOT send bug reports or code via email to individual developers.
for reporting any bugs in GASNet. You may find an instant solution to your problem by searching the bug database!
We are interested in supporting GASNet on as wide a variety of HPC
systems as possible. If your system or network is not supported and you are
willing to let us use your resources for development, please contact us!
We very much appreciate your feedback. Thank you for using GASNet!