ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
74 Commits 22 Branches 45 Tags 86 MiB
C 84.4%
Shell 8.7%
Python 5.3%
Makefile 1.2%
C++ 0.3%
3adea82331
Go to file
Daniel Verkamp 3adea82331 build: always build with -fPIC 
This allows the same objects to be linked into static and shared
libraries and allows the creation of position-independent executables
with the static libraries.

Change-Id: I119949c3644c02a83e414227615dcc2d8f896286
Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-10-13 10:12:54 -07:00
doc doc: remove reference to nonexistent images dir 2015-09-24 11:24:16 -07:00
examples util: add sprintf_alloc() function 2015-10-06 10:40:51 -07:00
include/spdk util: add sprintf_alloc() function 2015-10-06 10:40:51 -07:00
lib util: add sprintf_alloc() function 2015-10-06 10:40:51 -07:00
mk build: always build with -fPIC 2015-10-13 10:12:54 -07:00
scripts autobuild: unbind NVMe devices on FreeBSD 2015-10-09 10:03:25 -07:00
test autotest: output timing in flamegraph format 2015-10-08 16:07:47 -07:00
.astylerc build: check formatting with astyle 2015-09-23 09:05:51 -07:00
.gitignore build: add CUnit-Memory-Dump.xml to .gitignore 2015-10-12 15:11:57 -07:00
autobuild.sh autotest: output timing in flamegraph format 2015-10-08 16:07:47 -07:00
autopackage.sh autotest: output timing in flamegraph format 2015-10-08 16:07:47 -07:00
autotest.sh autobuild: unbind NVMe devices on FreeBSD 2015-10-09 10:03:25 -07:00
CONFIG SPDK: Initial check-in 2015-09-21 08:52:41 -07:00
LICENSE SPDK: Initial check-in 2015-09-21 08:52:41 -07:00
Makefile SPDK: Initial check-in 2015-09-21 08:52:41 -07:00
PORTING.md Add porting guide. 2015-09-28 09:07:19 -07:00
README.md Add porting guide. 2015-09-28 09:07:19 -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.

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.1.0.tar.gz
3) tar xfz dpdk-2.1.0.tar.gz
4) cd dpdk-2.1.0

Linux:

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

FreeBSD:

5) gmake install T=x86_64-native-bsdapp-clang

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=`pwd`/dpdk-2.1.0/x86_64-native-linuxapp-gcc

FreeBSD:

gmake DPDK_DIR=`pwd`/dpdk-2.1.0/x86_64-native-bsdapp-clang

Hugepages and Device Binding

Before running an SPDK application, some hugepages must be allocated and any NVMe devices must be unbound from the native NVMe kernel driver. SPDK includes scripts to automate this process on both Linux and FreeBSD.

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