History

Tomasz Zawadzki 6c54c13cd4 event/subsystem/bdev: asynchronous SPDK finish First this change moves spdk_subsystem_fini() to trigger on spdk_app_stop(). This ensures that spdk_subsystem_fini() is called before reactors are stopped in spdk_reactors_stop(). Finish paths for subsystems, bdevs and copy engine is now asynchronous. Each of those three mentioned have to make sure they are asynchronous as well. Only bdev that currently has requirement for asynchronous finish are logical volume. Thus the change in vbdev_lvol.c making it move to next bdev module only after all lvol stores were unloaded. Fio_plugin finish of bdev and copy_engine was removed for now. Next patch in series adds it back with async support. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I80ee2d084f3d82c50bf1329e08996604ae61b1b3 Reviewed-on: https://review.gerrithub.io/381536 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>		2017-10-27 13:03:55 -04:00
..
.gitignore	bdev: Add an example fio plugin	2017-08-04 20:03:37 -04:00
bdev.conf.in	bdev: Add an example fio plugin	2017-08-04 20:03:37 -04:00
example_config.fio	bdev: Add an example fio plugin	2017-08-04 20:03:37 -04:00
fio_plugin.c	event/subsystem/bdev: asynchronous SPDK finish	2017-10-27 13:03:55 -04:00
full_bench.fio	bdev: Add an example fio plugin	2017-08-04 20:03:37 -04:00
Makefile	bdev: Add an example fio plugin	2017-08-04 20:03:37 -04:00
README.md	bdev: Add an example fio plugin	2017-08-04 20:03:37 -04:00

README.md

Compiling fio

Clone the fio source repository from https://github.com/axboe/fio

git clone https://github.com/axboe/fio

Then check out the fio 2.21:

cd fio && git checkout fio-2.21

Finally, compile the code:

make

Compiling SPDK

Clone the SPDK source repository from https://github.com/spdk/spdk

git clone https://github.com/spdk/spdk
git submodule update --init

Then, run the SPDK configure script to enable fio (point it to the root of the fio repository):

cd spdk
./configure --with-fio=/path/to/fio/repo <other configuration options>

Finally, build SPDK:

make

Note to advanced users: These steps assume you're using the DPDK submodule. If you are using your own version of DPDK, the fio plugin requires that DPDK be compiled with -fPIC. You can compile DPDK with -fPIC by modifying your DPDK configuration file and adding the line:

EXTRA_CFLAGS=-fPIC

Usage

To use the SPDK fio plugin with fio, specify the plugin binary using LD_PRELOAD when running fio and set ioengine=spdk_bdev in the fio configuration file (see example_config.fio in the same directory as this README).

LD_PRELOAD=<path to spdk repo>/examples/bdev/fio_plugin/fio_plugin fio

The fio configuration file must contain one new parameter:

spdk_conf=./examples/bdev/fio_plugin/bdev.conf

This must point at an SPDK configuration file. There are a number of example configuration files in the SPDK repository under etc/spdk.

You can specify which block device to run against by setting the filename parameter to the block device name:

filename=Malloc0

Or for NVMe devices:

filename=Nvme0n1

Currently the SPDK fio plugin is limited to the thread usage model, so fio jobs must also specify thread=1 when using the SPDK fio plugin.

fio also currently has a race condition on shutdown if dynamically loading the ioengine by specifying the engine's full path via the ioengine parameter - LD_PRELOAD is recommended to avoid this race condition.

When testing random workloads, it is recommended to set norandommap=1. fio's random map processing consumes extra CPU cycles which will degrade performance over time with the fio_plugin since all I/O are submitted and completed on a single CPU core.