PMwCAS is a library that allows atomically changing multiple 8-byte words on non-volatile memory in a lock-free manner. It allows developers to easily build lock-free data structures for non-volatile memory and requires no custom recovery logic from the application. More details are described in the following slide deck, full paper and extended abstract:
Easy Lock-Free Indexing in Non-Volatile Memory.
Tianzheng Wang, Justin Levandoski and Paul Larson.
ICDE 2018.
Easy Lock-Free Programming in Non-Volatile Memory.
Tianzheng Wang, Justin Levandoski and Paul Larson.
NVMW 2019.
Finalist for Memorable Paper Award.
Suppose we build in a separate directory "build" under the source directory.
$ mkdir build && cd build
$ cmake -DPMEM_BACKEND=[PMDK/Volatile/Emu] \ # persistent memory backend
-DDESC_CAP=[4/5/6/...] \ # descriptor capacity
-DWITH_RTM=[0/1] \ # Use Intel RTX
..
$ make -jNBy default each descriptor can hold up to four words. This can be adjusted at compile-time by specifying the DESC_CAP parameter to CMake, for example the following will allow up to 8 words per descriptor:
$ cmake -DDESC_CAP=8 [...]
The current code supports three variants with different persistence modes:
- Persistence using Intel PMDK
- Persistence by emulation with DRAM
- Volatile (no persistence support)
A persistence mode must be specified at build time through the PMEM_BACKEND option in CMake (default PMDK).
The central concept of PMwCAS is desrciptors. The typical steps to change multiple 8-byte words are:
- Allocate a descriptor;
- Fill in the descriptor with the expected and new values of each target word;
- Issue the PMwCAS command to actually conduct the operation.
The target words often are pointers to dynamically allocated memory blocks. PMwCAS allows transparent handling of dynamically allocated memory depending on user-specified policy. For example, one can specify to allocate a memory block and use it as the 'new value' of a target word, and specify that this memory block be deallocated if the PMwCAS failed.
See APIs.md for a list of useful APIs and memory related polices and examples.
It is important to note that PMwCAS uses C++11 thread_local variables which must be reset if the descriptor pool is destructed and/or a thread is (in rare cases) re-purposed to use a different descriptor pool later. The library provides a Thread abstraction that extends std::thread for this purpose. The user application is expected to use the Thread class whenever std::thread is needed. Thread has the exactly same APIs as std::thread with an overloaded join() interface that clears its own thread-local variables upon exit. The Thread class also provides a static ClearRegistry() function that allows the user application to clear all thread local variables. All the user application needs is to invoke this function upon changing/destroying a descriptor pool.
For example, the below pattern is often used in our test cases:
DescriptorPool pool_1 = new DescriptorPool(...); // Create a descriptor pool
... use pool_1 ...
delete pool_1;
Thread::ClearRegistry(); // Reset the TLS variables, after this it is safe to use another pool
DescriptorPool *pool_2 = new DescriptorPool(...);
... use pool_2 ...
Thread::ClearRegistry();
We seperate the benchmark code into a independent repo to automatically and continously track PMwCAS performance.
Check out our benchmark repo for more details.
We welcome all contributions.
Licensed under the MIT License.