Skip to content
Min Si edited this page Nov 13, 2017 · 4 revisions

About Casper

Although one-sided communication semantics can asynchronously handle communication progress, the MPI standard does not guarantee it to be truly asynchronous. In most network interfaces, complex one-sided communication operations such as noncontiguous accumulate are not natively supported. MPI implementations still require the target process to make MPI calls in order to ensure completion of such operations.

Casper is a process-based asynchronous progress model for MPI RMA communication on multicore and many-core architectures. The central idea of Casper is to keep aside a small, user-specified number of cores on a multicore or many-core environment as “ghost processes,” which are dedicated to help asynchronous progress for user processes through appropriate memory mapping from those user processes.

More information of Casper can be found at the project homepage: http://www.mcs.anl.gov/project/casper

Test Status

Travis Build with [MPICH v3.3a2 | OpenMPI v3.0, OSX | Ubuntu] Travis Build Status

Jenkins Build with [MPICH v3.2.1, Casper test suite | ARMCI-MPI test suite | MPICH test suite]

Support and Bug Reporting

If you have problems that need any assistance about the Casper installation and usage, or you have found a bug in Casper, please contact [email protected] mailing list. In order to avoid spam, we request you to subscribe to this list before sending an email.
Clone this wiki locally