fio: add xnvme engine
A message that is not in the archive (sent off-list or not yet received): CGME20220511163552epcas5p4c2e1b204a47a543c24f84da89ef0c89a@epcas5p4.samsung.com
v2 cover fio: add xnvme engine
This patch introduces a new xnvme fio engine.
xNVMe provides an API for synchronous and asynchronous I/O.
A library backs the API, libxnvme, which provides implementations for API users to run their I/O application on Linux, FreeBSD, macOS, and Windows without changing the application code.
Implementations of sync. interfaces include:
* psync (preadv/pwritev)
* Linux NVMe driver-ioctl
* FreeBSD NVMe driver-ioctl
Implementations of async. interfaces include:
* io_uring
* io_uring_cmd (experimental)
* libaio
* POSIX aio
In addition to the OS-managed interfaces, the library also utilize user-space NVMe-drivers
e.g. the SPDK NVMe/driver. Furthermore, "async-fallbacks" provide "async-emulation" in a sequential form and using a thread pool. Finally, a "nil" implementation is available to evaluate encapsulation/library overhead.
The xNVMe C API currently supports Windows interfaces: Windows Storport, IOCP, and experimental io_ring. However, these are not functional with the engine due to a few missing dependencies.
For more info on visit
https://xnvme.io
https://github.com/OpenMPDK/xNVMe
This patch also includes two example job files for Conventinal and ZNS specific commands.
In addition, it demonstrates how to instrument the engine to use different interfaces and with a user-space NVMe driver.
Changes since v1:
- Addressed review comments from Vincent.
- Improved error-logging and debugging by replacing XNVME_DEBUG with log_err, log_info and dprintf.
- Fixed issues when enabling iovec-payloads, now using io_u->mmap_data instead of io_u->engine_data as it gets overwritten by io_u->index.
Ankit Kumar (3):
engines/xnvme: add xnvme engine
docs: documentation for xnvme ioengine
examples: add example job file for xnvme engine usage
HOWTO.rst | 55 ++- Makefile | 7 +- configure | 22 + engines/xnvme.c | 981 +++++++++++++++++++++++++++++++++++++ examples/xnvme-compare.fio | 72 +++ examples/xnvme-zoned.fio | 87 ++++ fio.1 | 70 ++- optgroup.h | 2 + options.c | 5 + 9 files changed, 1296 insertions(+), 5 deletions(-) create mode 100644 engines/xnvme.c create mode 100644 examples/xnvme-compare.fio create mode 100644 examples/xnvme-zoned.fio
Signature · 1 line
2.17.1
PATCH v2 1/3 engines/xnvme: add xnvme engine
This patch introduces a new fio engine to work with xNVMe >= 0.2.0. xNVMe provides a user space library (libxnvme) to work with NVMe devices. The NVMe driver being used by libxnvme is re-targetable and can be any one of the GNU/Linux Kernel NVMe driver via libaio, IOCTLs, io_uring, the SPDK NVMe driver, or your own custom NVMe driver.
For more info visit https://xnvme.io
https://github.com/OpenMPDK/xNVMe
--- Makefile | 7 +- configure | 22 ++ engines/xnvme.c | 981 ++++++++++++++++++++++++++++++++++++++++++++++++ optgroup.h | 2 + options.c | 5 + 5 files changed, 1016 insertions(+), 1 deletion(-) create mode 100644 engines/xnvme.c
Makefile +6 -1
@@ -223,7 +223,12 @@ ifdef CONFIG_LIBZBC libzbc_LIBS = -lzbc ENGINES += libzbc endif - +ifdef CONFIG_LIBXNVME + xnvme_SRCS = engines/xnvme.c + xnvme_LIBS = $(LIBXNVME_LIBS) + xnvme_CFLAGS = $(LIBXNVME_CFLAGS) + ENGINES += xnvme +endif ifeq ($(CONFIG_TARGET_OS), Linux) SOURCE += diskutil.c fifo.c blktrace.c cgroup.c trim.c engines/sg.c \ oslib/linux-dev-lookup.c engines/io_uring.c
configure +22 -0
@@ -171,6 +171,7 @@ march_set="no" libiscsi="no" libnbd="no" libnfs="no" +xnvme="no" libzbc="" dfs="" dynamic_engines="no"
@@ -240,6 +241,8 @@ for opt do ;; --disable-libzbc) libzbc="no" ;; + --enable-xnvme) xnvme="yes" + ;; --disable-tcmalloc) disable_tcmalloc="yes" ;; --disable-nfs) disable_nfs="yes"
@@ -291,6 +294,7 @@ if test "$show_help" = "yes" ; then echo "--with-ime= Install path for DDN's Infinite Memory Engine" echo "--enable-libiscsi Enable iscsi support" echo "--enable-libnbd Enable libnbd (NBD engine) support" + echo "--enable-xnvme Enable xnvme support" echo "--disable-libzbc Disable libzbc even if found" echo "--disable-tcmalloc Disable tcmalloc support" echo "--dynamic-libengines Lib-based ioengines as dynamic libraries"
@@ -2583,6 +2587,19 @@ if test "$libzbc" != "no" ; then fi print_config "libzbc engine" "$libzbc" +########################################## +# Check if we have xnvme +if test "$xnvme" != "yes" ; then + if check_min_lib_version xnvme 0.2.0; then + xnvme="yes" + xnvme_cflags=$(pkg-config --cflags xnvme) + xnvme_libs=$(pkg-config --libs xnvme) + else + xnvme="no" + fi +fi +print_config "xnvme engine" "$xnvme" + ########################################## # check march=armv8-a+crc+crypto if test "$march_armv8_a_crc_crypto" != "yes" ; then
@@ -3190,6 +3207,11 @@ if test "$libnfs" = "yes" ; then echo "LIBNFS_CFLAGS=$libnfs_cflags" >> $config_host_mak echo "LIBNFS_LIBS=$libnfs_libs" >> $config_host_mak fi +if test "$xnvme" = "yes" ; then + output_sym "CONFIG_LIBXNVME" + echo "LIBXNVME_CFLAGS=$xnvme_cflags" >> $config_host_mak + echo "LIBXNVME_LIBS=$xnvme_libs" >> $config_host_mak +fi if test "$dynamic_engines" = "yes" ; then output_sym "CONFIG_DYNAMIC_ENGINES" fi
engines/xnvme.c new file +981 -0
981 lines not on this page · raw message
optgroup.h +2 -0
@@ -72,6 +72,7 @@ enum opt_category_group { __FIO_OPT_G_DFS, __FIO_OPT_G_NFS, __FIO_OPT_G_WINDOWSAIO, + __FIO_OPT_G_XNVME,FIO_OPT_G_RATE = (1ULL << __FIO_OPT_G_RATE), FIO_OPT_G_ZONE = (1ULL << __FIO_OPT_G_ZONE),
@@ -118,6 +119,7 @@ enum opt_category_group {FIO_OPT_G_LIBCUFILE = (1ULL << __FIO_OPT_G_LIBCUFILE),FIO_OPT_G_DFS = (1ULL << __FIO_OPT_G_DFS),FIO_OPT_G_WINDOWSAIO = (1ULL << __FIO_OPT_G_WINDOWSAIO), + FIO_OPT_G_XNVME = (1ULL << __FIO_OPT_G_XNVME), };extern const struct opt_group *opt_group_from_mask (uint64_t *mask);
options.c +5 -0
@@ -2144,6 +2144,11 @@ struct fio_option fio_options[FIO_MAX_OPTS] = { { .ival = "nfs", .help = "NFS IO engine", }, +#endif +#ifdef CONFIG_LIBXNVME + { .ival = "xnvme", + .help = "XNVME IO engine", + }, #endif }, },
Signature · 1 line
2.17.1
PATCH v2 2/3 docs: documentation for xnvme ioengine
In reply to Ankit Kumar--- HOWTO.rst | 55 +++++++++++++++++++++++++++++++++++++++++-- fio.1 | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++-- 2 files changed, 121 insertions(+), 4 deletions(-)
HOWTO.rst +53 -2
@@ -2171,6 +2171,12 @@ I/O engine **exec** Execute 3rd party tools. Could be used to perform monitoring during jobs runtime. + **xnvme** + I/O engine using the xNVMe C API, for NVMe devices. The xnvme engine provides + flexibility to access GNU/Linux Kernel NVMe driver via libaio, IOCTLs, io_uring, + the SPDK NVMe driver, or your own custom NVMe driver. The xnvme engine includes + engine specific options. (See https://xnvme.io). + I/O engine specific parameters ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -2260,7 +2266,7 @@ with the caveat that when used on the command line, they must come after the making the submission and completion part more lightweight. Required for the below :option:`sqthread_poll` option. -.. option:: sqthread_poll : [io_uring] +.. option:: sqthread_poll : [io_uring] [xnvme] Normally fio will submit IO by issuing a system call to notify the kernel of available items in the SQ ring. If this option is set, the
@@ -2275,7 +2281,7 @@ with the caveat that when used on the command line, they must come after the .. option:: hipri - [io_uring] + [io_uring], [xnvme] If this option is set, fio will attempt to use polled IO completions. Normal IO completions generate interrupts to signal the completion of
@@ -2725,6 +2731,51 @@ with the caveat that when used on the command line, they must come after the If set, stdout and stderr streams are redirected to files named from the job name. Default is true. +.. option:: xnvme_async=str : [xnvme] + + Select the xnvme async command interface. This can take these values. + + **emu** + This is default and used to emulate asynchronous I/O. + **thrpool** + Use thread pool for Asynchronous I/O. + **io_uring** + Use Linux io_uring/liburing for Asynchronous I/O. + **libaio** + Use Linux aio for Asynchronous I/O. + **posix** + Use POSIX aio for Asynchronous I/O. + **nil** + Use nil-io; For introspective perf. evaluation + +.. option:: xnvme_sync=str : [xnvme] + + Select the xnvme synchronous command interface. This can take these values. + + **nvme** + This is default and uses Linux NVMe Driver ioctl() for synchronous I/O. + **psync** + Use pread()/write() for synchronous I/O. + +.. option:: xnvme_admin=str : [xnvme] + + Select the xnvme admin command interface. This can take these values. + + **nvme** + This is default and uses linux NVMe Driver ioctl() for admin commands. + **block** + Use Linux Block Layer ioctl() and sysfs for admin commands. + **file_as_ns** + Use file-stat to construct NVMe idfy responses. + +.. option:: xnvme_dev_nsid=int : [xnvme] + + xnvme namespace identifier, for userspace NVMe driver. + +.. option:: xnvme_iovec=int : [xnvme] + + If this option is set. xnvme will use vectored read/write commands. + I/O depth ~~~~~~~~~
fio.1 +68 -2
94 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH v2 3/3 examples: add example job file for xnvme engine usage
In reply to Ankit Kumar--- examples/xnvme-compare.fio | 72 +++++++++++++++++++++++++++++++ examples/xnvme-zoned.fio | 87 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 159 insertions(+) create mode 100644 examples/xnvme-compare.fio create mode 100644 examples/xnvme-zoned.fio
examples/xnvme-compare.fio new file +72 -0
@@ -0,0 +1,72 @@ +; Compare fio IO engines with a random-read workload using BS=4k at QD=1 +; +; README +; +; This job-file is intended to be used as: +; +; # Use the built-in io_uring engine to get baseline numbers +; fio examples/xnvme-compare.fio \ +; --section=default \ +; --ioengine=io_uring \ +; --sqthread_poll=1 \ +; --filename=/dev/nvme0n1 +; +; # Use the xNVMe io-engine engine with Linux backend and io_uring async. impl. +; fio examples/xnvme-compare.fio \ +; --section=default \ +; --ioengine=xnvme \ +; --sqthread_poll=1 \ +; --xnvme_async=io_uring \ +; --filename=/dev/nvme0n1 +; +; # Use the xNVMe io-engine engine with Linux backend and libaio async. impl. +; fio examples/xnvme-compare.fio \ +; --section=default \ +; --ioengine=xnvme \ +; --xnvme_async=libaio \ +; --filename=/dev/nvme0n1 +; +; # Use the xNVMe io-engine engine with SPDK backend, note that you have to set the Namespace-id +; fio examples/xnvme-compare.fio \ +; --section=default \ +; --ioengine=xnvme \ +; --xnvme_dev_nsid=1 \ +; --filename=0000\\:01\\:00.0 +; +; NOTE: The URI encoded in the filename above, the ":" must be escaped. +; +; On the command-line using two "\\": +; +; --filename=0000\\:01\\:00.0 +; +; Within a fio-script using a single "\": +; +; filename=0000\:01\:00.0 +; +; NOTE: If you want to override the default bs, iodepth, and workload, then +; invoke it as: +; +; FIO_BS="512" FIO_RW="verify" FIO_IODEPTH=16 fio examples/xnvme-compare.fio \ +; --section=override +; +[global] +rw=randread +size=12G +iodepth=1 +bs=4K +direct=1 +thread=1 +time_based=1 +runtime=7 +ramp_time=3 +norandommap=1 + +; Avoid accidentally creating device files; e.g. "/dev/nvme0n1", "/dev/nullb0" +allow_file_create=0 + +[default] + +[override] +rw=${FIO_RW} +iodepth=${FIO_IODEPTH} +bs=${FIO_BS}
examples/xnvme-zoned.fio new file +87 -0
87 lines not on this page · raw message
Signature · 1 line
2.17.1
Quoted 11 lines · Ankit Kumar
This patch introduces a new xnvme fio engine.
xNVMe provides an API for synchronous and asynchronous I/O.
A library backs the API, libxnvme, which provides implementations for API users to run their I/O application on Linux, FreeBSD, macOS, and Windows without changing the application code.Implementations of sync. interfaces include:
* psync (preadv/pwritev)
* Linux NVMe driver-ioctl
* FreeBSD NVMe driver-ioctl
Quoted 5 lines
Implementations of async. interfaces include:
*io_uring
*io_uring_cmd(experimental)
* libaio
* POSIX aio
Is the plan also to cleanup the passthrough support for the io_uring engine and submit that? I'd personally find that a lot more useful than this xnvme engine. I don't mind including it if you guys are using it and find it useful for testing xnvme on various platforms, but it's not something I'd personally use.
Signature · 1 line
Jens Axboe
Yes we are using xnvme on various platforms, and it would be great if it gets included as part of FIO.
For supporting io_uring engine with passthrough, yes we also have a plan in place to clean up the code and send it for review.
Quoted 28 lines · Jens Axboe
Quoted 11 lines · Ankit Kumar
This patch introduces a new xnvme fio engine.
xNVMe provides an API for synchronous and asynchronous I/O.
A library backs the API, libxnvme, which provides implementations for API users to run their I/O application on Linux, FreeBSD, macOS, and Windows without changing the application code.Implementations of sync. interfaces include:
* psync (preadv/pwritev)
* Linux NVMe driver-ioctl
* FreeBSD NVMe driver-ioctlQuoted 5 lines
Implementations of async. interfaces include:
*io_uring
*io_uring_cmd(experimental)
* libaio
* POSIX aioIs the plan also to cleanup the passthrough support for the
io_uringengine and submit that? I'd personally find that a lot more useful than this xnvme engine. I don't mind including it if you guys are using it and find it useful for testing xnvme on various platforms, but it's not something I'd personally use.--
Jens Axboe
Quoted 4 lines · Ankit Kumar
Yes we are using xnvme on various platforms, and it would be great if it gets included as part of FIO.
For supportingio_uringengine with passthrough, yes we also have a plan in place to clean up the code and send it for review.
Sounds good. I've applied the xvnme engine, would appreciate if we can do the passthrough one shortly too. I'm wondering if that one is best done as a separate engine too - it could still be in engines/io_uring.c but have a separate ioengine_ops to keep the code nicely separated while still being able to use the same helpers in there.
Signature · 1 line
Jens Axboe
Thanks a lot for applying the xnvme engine changes. Yes we are adding passthrough support in io_uring by having a separate ioengine_ops. The changes will be ready shortly.
Quoted 16 lines · Jens Axboe
Quoted 4 lines · Ankit Kumar
Yes we are using xnvme on various platforms, and it would be great if it gets included as part of FIO.
For supportingio_uringengine with passthrough, yes we also have a plan in place to clean up the code and send it for review.Sounds good. I've applied the xvnme engine, would appreciate if we can do the passthrough one shortly too. I'm wondering if that one is best done as a separate engine too - it could still be in
engines/io_uring.cbut have a separateioengine_opsto keep the code nicely separated while still being able to use the same helpers in there.--
Jens Axboe
Jens Axboe
AppliedQuoted 6 lines · Ankit Kumar
This patch introduces a new xnvme fio engine.
xNVMe provides an API for synchronous and asynchronous I/O.
A library backs the API, libxnvme, which provides implementations for API users to run their I/O application on Linux, FreeBSD, macOS, and Windows without changing the application code.
Quoted 6 lines
Implementations of sync. interfaces include:
* psync (preadv/pwritev)
* Linux NVMe driver-ioctl
* FreeBSD NVMe driver-ioctl[...]
Applied, thanks!
[1/3] engines/xnvme: add xnvme engine
commit: a3ff873ed4e7eed863927d749f39560068d40940
[2/3] docs: documentation for xnvme ioengine
commit: 454154e66e93b3dc314955c197a21eeacbe69c78
[3/3] examples: add example job file for xnvme engine usage
commit: d338e8760f3f442b3e4498598854130e55745eb9Best regards,
Signature · 1 line
Jens Axboe