Go to file

Daniel Verkamp b96536e74a nvme: check request allocation when submitting AER Previously, if nvme_allocate_request() failed in nvme_ctrlr_construct_and_submit_aer(), there was no error checking, so a NULL pointer would be dereferenced. Add a return value to nvme_ctrlr_construct_and_submit_aer() so we can signal failure to the caller. This can only really be reasonably handled during initialization; when resubmitting a completed AER later, there is nowhere to report failure, so the AER will just remain unsubmitted. Change-Id: I413eb6c21be01cd9a61e67f62f2d0b7170eabaa3 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>		2016-01-06 13:51:15 -07:00
doc	ioat: add user-mode Intel I/OAT driver	2015-12-09 10:14:15 -07:00
examples	nvme/perf: don't crash if no namespaces are usable	2016-01-05 08:05:43 -07:00
include/spdk	SPDK: Add Intel vendor-specific log pages and data structures.	2016-01-04 15:22:17 -07:00
lib	nvme: check request allocation when submitting AER	2016-01-06 13:51:15 -07:00
mk	build: undefine _FORTIFY_SOURCE before setting it	2015-12-22 10:15:06 -07:00
scripts	autotest: use generic DPDK path on Linux	2016-01-05 13:31:07 -07:00
test	nvme/reset: don't crash if no namespaces are usable	2016-01-06 12:21:04 -07:00
.astylerc	build: check formatting with astyle	2015-09-23 09:05:51 -07:00
.gitignore	build: add CONFIG_COVERAGE code coverage option	2015-11-02 14:40:49 -07:00
.travis.yml	build: add Travis CI integration	2015-11-04 11:05:59 -07:00
autobuild.sh	autobuild: add sleep to fix dependency test	2015-11-03 15:19:36 -07:00
autopackage.sh	CONFIG: allow overriding options in make command	2015-10-22 12:24:57 -07:00
autotest.sh	ioat: add user-mode Intel I/OAT driver	2015-12-09 10:14:15 -07:00
CONFIG	ioat: add user-mode Intel I/OAT driver	2015-12-09 10:14:15 -07:00
LICENSE	SPDK: Initial check-in	2015-09-21 08:52:41 -07:00
Makefile	build: allow make to work from any directory	2015-11-04 10:19:08 -07:00
PORTING.md	Add porting guide.	2015-09-28 09:07:19 -07:00
README.md	README: update to DPDK 2.2.0	2016-01-05 13:18:21 -07:00
unittest.sh	ioat: add user-mode Intel I/OAT driver	2015-12-09 10:14:15 -07:00

README.md

Storage Performance Development Kit

SPDK on 01.org

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.

Documentation

Doxygen API documentation

Porting Guide

Prerequisites

To build SPDK, some dependencies must be installed.

Fedora/CentOS:

gcc
libpciaccess-devel
CUnit-devel

Ubuntu/Debian:

gcc
libpciaccess-dev
make
libcunit1-dev

FreeBSD:

gcc
libpciaccess
gmake
cunit

Additionally, DPDK is required.

1) cd /path/to/spdk
2) wget http://dpdk.org/browse/dpdk/snapshot/dpdk-2.2.0.tar.gz
3) tar xfz dpdk-2.2.0.tar.gz
4) cd dpdk-2.2.0

Linux:

5) make install T=x86_64-native-linuxapp-gcc DESTDIR=.

FreeBSD:

5) 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-2.2.0/x86_64-native-linuxapp-gcc

FreeBSD:

gmake DPDK_DIR=./dpdk-2.2.0/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 scripts to automate this process on both Linux and FreeBSD.

1) scripts/configure_hugepages.sh
2) scripts/unbind.sh