numam-spdk/README.md
Daniel Verkamp 326a0224b2 readme: convert list of features into doc links
Change-Id: I01fa93ca51576c5b356fc2193f81e210ef411908
Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-09-28 08:20:09 -07:00

110 lines
3.2 KiB
Markdown

Storage Performance Development Kit
===================================
[![Build Status](https://travis-ci.org/spdk/spdk.svg?branch=master)](https://travis-ci.org/spdk/spdk)
[SPDK Mailing List](https://lists.01.org/mailman/listinfo/spdk)
[SPDK on 01.org](https://01.org/spdk)
The Storage Performance Development Kit (SPDK) provides a set of tools
and libraries for writing high performance, scalable, user-mode storage
applications. It achieves high performance by moving all of the necessary
drivers into userspace and operating in a polled mode instead of relying on
interrupts, which avoids kernel context switches and eliminates interrupt
handling overhead.
The development kit currently includes:
* [NVMe driver](http://www.spdk.io/spdk/doc/nvme.html)
* [I/OAT (DMA engine) driver](http://www.spdk.io/spdk/doc/ioat.html)
* [NVMe over Fabrics target](http://www.spdk.io/spdk/doc/nvmf.html)
* [iSCSI target](http://www.spdk.io/spdk/doc/iscsi.html)
Documentation
=============
[Doxygen API documentation](http://spdk.io/spdk/doc/) is available, as
well as a [Porting Guide](PORTING.md) for porting SPDK to different frameworks
and operating systems.
Many examples are available in the `examples` directory.
[Changelog](CHANGELOG.md)
Prerequisites
=============
To build SPDK, some dependencies must be installed.
Fedora/CentOS:
sudo dnf install -y gcc gcc-c++ libpciaccess-devel CUnit-devel libaio-devel openssl-devel
# Additional dependencies for NVMe over Fabrics:
sudo dnf install -y libibverbs-devel librdmacm-devel
Ubuntu/Debian:
sudo apt-get install -y gcc g++ libpciaccess-dev make libcunit1-dev libaio-dev libssl-dev
# Additional dependencies for NVMe over Fabrics:
sudo apt-get install -y libibverbs-dev librdmacm-dev
FreeBSD:
- gcc
- libpciaccess
- gmake
- cunit
- openssl
Additionally, [DPDK](http://dpdk.org/doc/quick-start) is required.
1) cd /path/to/spdk
2) wget http://fast.dpdk.org/rel/dpdk-16.07.tar.xz
3) tar xf dpdk-16.07.tar.xz
Linux:
4) (cd dpdk-16.07 && make install T=x86_64-native-linuxapp-gcc DESTDIR=.)
FreeBSD:
4) (cd dpdk-16.07 && gmake install T=x86_64-native-bsdapp-clang DESTDIR=.)
Building
========
Once the prerequisites are installed, run 'make' within the SPDK directory
to build the SPDK libraries and examples.
make DPDK_DIR=/path/to/dpdk
If you followed the instructions above for building DPDK:
Linux:
make DPDK_DIR=./dpdk-16.07/x86_64-native-linuxapp-gcc
FreeBSD:
gmake DPDK_DIR=./dpdk-16.07/x86_64-native-bsdapp-clang
Hugepages and Device Binding
============================
Before running an SPDK application, some hugepages must be allocated and
any NVMe and I/OAT devices must be unbound from the native kernel drivers.
SPDK includes a script to automate this process on both Linux and FreeBSD.
This script should be run as root.
sudo scripts/setup.sh
Examples
========
Example code is located in the examples directory. The examples are compiled
automatically as part of the build process. Simply call any of the examples
with no arguments to see the help output. You'll likely need to run the examples
as a privileged user (root) unless you've done additional configuration
to grant your user permission to allocate huge pages and map devices through
vfio.