This is the top-level README.md of the Persistent Memory Development Kit. For more information, see http://pmem.io.
Bugs and feature requests are tracked in our GitHub Issues Database.
Please see the file LICENSE for information on how this library is licensed.
This tree contains a collection of libraries for using Non-Volatile Memory (NVM). There are currently nine libraries:
- libpmem -- basic pmem operations like flushing
- libpmemblk, libpmemlog, libpmemobj -- pmem transactions
- libvmem, libvmmalloc1 -- volatile use of pmem
- libpmempool -- persistent memory pool management
- librpmem1 -- remote access to persistent memory (EXPERIMENTAL)
- libpmemcto -- close-to-open persistence (EXPERIMENTAL)
and two command-line utilities:
- pmempool -- standalone tool for off-line pool management
- daxio -- perform I/O on Device-DAX devices or zero a Device-DAX device
These libraries and utilities are described in more detail on the pmem web site. There you'll find man pages, examples, and tutorials.
Currently, these libraries only work on 64-bit Linux, Windows2 and 64-bit FreeBSD 11+3.
1 Not supported on Windows.
2 PMDK for Windows is feature complete, but not yet considered production quality.
3 DAX and libfabric are not yet supported in FreeBSD, so at this time PMDK is available as a technical preview release for development purposes.
If you want to install these libraries to try them out of your system, you can either install pre-built packages, which we build for every stable release, or clone the tree and build it yourself.
Builds are tagged something like 0.2+b1, which means
Build 1 on top of version 0.2 and 0.2-rc3, which means
Release Candidate 3 for version 0.2. Stable releases
are the simpler major.minor tags like 0.2. To find
pre-build packages, check the Downloads associated with
the stable releases on the
github release page.
The source tree is organized as follows:
- doc -- man pages describing each library contained here
- src -- the source for the libraries
- src/include -- public header files for all the libraries
- src/benchmarks -- benchmarks used by development team
- src/examples -- brief example programs using these libraries
- src/freebsd -- FreeBSD-specific header files
- src/test -- unit tests used by development team
- src/tools -- various tools developed for PMDK
- src/windows -- Windows-specific source and header files
- utils -- utilities used during build & test
- CONTRIBUTING.md -- instructions for people wishing to contribute
- CODING_STYLE.md -- coding standard and conventions for PMDK
To build this library on Linux, you may need to install the following required packages on the build system:
- autoconf
- pkg-config
The following packages are required only by selected PMDK components or features. If not present, those components or features may not be available:
- libfabric (v1.4.2 or later) -- required by librpmem
- ndctl and daxctl (v60.1 or later) -- required by daxio and RAS features
On Windows, to build PMDK and run the tests you need:
- MS Visual Studio 2015
- Windows SDK 10.0.16299.15
- perl (i.e. ActivePerl)
- PowerShell 5
To build and test this library on FreeBSD, you may need to install the following required packages on the build system:
- autoconf
- bash
- binutils
- coreutils
- e2fsprogs-libuuid
- gmake
- libunwind
- ncurses4
- pkgconf
Some tests and example applications require additional packages, but they do not interrupt building if they are missing. An appropriate message is displayed instead. For details please read the DEPENDENCIES section in the appropriate README file.
See our Dockerfiles to get an idea what packages are required to build the entire PMDK, with all the tests and examples on the Travis-CI system.
4 The pkg version of ncurses is required for proper operation; the base version included in FreeBSD is not sufficient.
To build the latest development version, just clone this tree and build the master branch:
$ git clone https://github.com/pmem/pmdk
$ cd pmdk
Once the build system is setup, the Persistent Memory Development Kit is built
using the make5 command at the top level:
$ make
If you want to compile, and hopefully run the builtin tests, with a different
compiler, you have to provide the CC and CXX variables. For example:
$ make CC=clang CXX=clang++
These variables are independent and setting CC=clang does not set CXX=clang++.
Once the make completes,6 all the libraries are built and the examples
under src/examples are built as well. You can play with the library
within the build tree, or install it locally on your machine. Installing
the library is more convenient since it installs man pages and libraries
in the standard system locations:
(as root...)
# make install
To install this library into other locations, you can use the prefix variable, e.g.:
$ make install prefix=/usr/local
This will install files to /usr/local/lib, /usr/local/include /usr/local/share/man.
To prepare this library for packaging, you can use the DESTDIR variable, e.g.:
$ make install DESTDIR=/tmp
This will install files to /tmp/usr/lib, /tmp/usr/include /tmp/usr/share/man.
The man pages (groff files) are generated as part of the install rule. To
generate the documentation separately, run:
$ make doc
DEPENDENCIES: doxygen, graphviz, pandoc7
To install a complete copy of the source tree to $(DESTDIR)/pmdk:
$ make source DESTDIR=some_path
To build rpm packages on rpm-based distributions:
$ make rpm
If you want to build packages without running tests, run:
$ make BUILD_PACKAGE_CHECK=n rpm
DEPENDENCIES: rpmbuild
To build dpkg packages on Debian-based distributions:
$ make dpkg
If you want to build packages without running tests, run:
$ make BUILD_PACKAGE_CHECK=n dpkg
DEPENDENCIES: devscripts
If you want to invoke make with the same variables multiple times, you can create user.mk file in the top level directory and put all variables there. For example:
$ cat user.mk
EXTRA_CFLAGS_RELEASE = -ggdb -fno-omit-frame-pointer
PATH += :$HOME/valgrind/bin
This feature is intended to be used only by developers and it may not work for all variables. Please do not file bug reports about it. Just fix it and make a PR.
5 For FreeBSD, use
gmakerather thanmake.6 By default all code is built with the -Werror flag, which fails the whole build when the compiler emits any warning. This is very useful during development, but can be annoying in deployment. If you want to disable -Werror, use the EXTRA_CFLAGS variable:
$ make EXTRA_CFLAGS="-Wno-error"
or
$ make EXTRA_CFLAGS="-Wno-error=$(type-of-warning)"
7Pandoc is provided by the hs-pandoc package on FreeBSD.
Before running the tests, you may need to prepare a test configuration file (src/test/testconfig.sh). Please see the available configuration settings in the example file (src/test/testconfig.sh.example).
To build and run the unit tests:
$ make check
To run a specific subset of tests, run for example:
$ make check TEST_TYPE=short TEST_BUILD=debug TEST_FS=pmem
To modify the timeout which is available for check type tests, run:
$ make check TEST_TIME=1m
This will set the timeout to 1 minute.
Please refer to the src/test/README for more details on how to run different types of tests.
The libraries support standard Valgrind drd, helgrind and memcheck, as well as a PM-aware version of Valgrind8. By default support for all tools is enabled. If you wish to disable it, supply the compiler with VG_<TOOL>_ENABLED flag set to 0, for example:
$ make EXTRA_CFLAGS=-DVG_MEMCHECK_ENABLED=0
VALGRIND_ENABLED flag, when set to 0, disables all Valgrind tools (drd, helgrind, memcheck and pmemcheck).8
The SANITIZE flag allows the libraries to be tested with various sanitizers. For example, to test the libraries with AddressSanitizer and UndefinedBehaviorSanitizer, run:
$ make SANITIZE=address,undefined clobber check
If you wish to run C++ standard library containers tests, you need to set the path to your custom versions of either gcc or libc++. For gcc run:
$ make USE_CUSTOM_GCC=1 GCC_INCDIR=/path/to/includes GCC_LIBDIR=/path/to/lib check
If you want to use a custom version of libc++ run:
$ make USE_LLVM_LIBCPP=1 LIBCPP_INCDIR=/path/to/includes/ LIBCPP_LIBDIR=/path/to/lib check
Please remember to set the appropriate versions of CC/CXX when using custom versions of the library.
For example, when using a custom version of libc++(version 3.9) installed to /usr/local/libcxx, to execute the tests run:
$ CC=clang CXX=clang++ make USE_LLVM_LIBCPP=1 LIBCPP_INCDIR=/usr/local/libcxx/include/c++/v1 LIBCPP_LIBDIR=/usr/local/libcxx/lib check
8 PM-aware Valgrind is not yet available for FreeBSD.
9 The address sanitizer is not supported for libvmmalloc on FreeBSD and will be ignored.
Clone the PMDK tree and open the solution:
> git clone https://github.com/pmem/pmdk
> cd pmdk/src
> devenv PMDK.sln
Select the desired configuration (Debug or Release) and build the solution (i.e. by pressing Ctrl-Shift-B).
Before running the tests, you may need to prepare a test configuration file (src/test/testconfig.ps1). Please see the available configuration settings in the example file (src/test/testconfig.ps1.example).
To run the unit tests, open the PowerShell console and type:
> cd pmdk/src/test
> RUNTESTS.ps1
To run a specific subset of tests, run for example:
> RUNTESTS.ps1 -b debug -t short
To run just one test, run for example:
> RUNTESTS.ps1 -b debug -i pmem_is_pmem
To modify the timeout, run:
> RUNTESTS.ps1 -o 3m
This will set the timeout to 3 minutes.
To display all the possible options, run:
> RUNTESTS.ps1 -h
Please refer to the src/test/README for more details on how to run different types of tests.
NOTE: The libfabric package required to build the librpmem and rpmemd is not yet available on stable Debian-based distributions. This makes it impossible to create Debian packages.
If you want to build Debian packages of librpmem and rpmemd run:
$ make RPMEM_DPKG=y dpkg
Some components in the source tree are treated as experimental. By default those components are built but not installed (and thus not included in packages).
If you want to build/install experimental packages run:
$ make EXPERIMENTAL=y [install,rpm,dpkg]
There is an initial support for 64-bit ARM processors provided, currently only for aarch64. All the PMDK libraries except librpmem can be built for 64-bit ARM. The examples, tools and benchmarks are not ported yet and may not get built on ARM cores. NOTE: The support for ARM processors is highly experimental. The libraries are only validated to "early access" quality with Cortex-A53 processor.
For more information on this library, contact Marcin Slusarz (marcin.slusarz@intel.com), Andy Rudoff (andy.rudoff@intel.com), or post to our Google group.