From: Ankit Kumar <ankit.kumar@samsung.com>
To: axboe@kernel.dk
Cc: fio@vger.kernel.org, krish.reddy@samsung.com,
simon.lund@samsung.com, Ankit Kumar <ankit.kumar@samsung.com>
Subject: [PATCH 0/3] fio: add xnvme engine
Date: Thu, 5 May 2022 18:49:32 +0530 [thread overview]
Message-ID: <20220505131935.32076-1-ankit.kumar@samsung.com> (raw)
In-Reply-To: CGME20220505132529epcas5p25512da35ba70c4eed9890f299b1db12f@epcas5p2.samsung.com
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.
Ankit Kumar (3):
engines/xnvme: add xnvme engine
docs: documentation for xnvme ioengine
examples: add example job file for xnvme engine usage
HOWTO.rst | 51 +-
Makefile | 7 +-
configure | 22 +
engines/xnvme.c | 1000 ++++++++++++++++++++++++++++++++++++
examples/xnvme-compare.fio | 72 +++
examples/xnvme-zoned.fio | 87 ++++
fio.1 | 67 ++-
optgroup.h | 2 +
options.c | 5 +
9 files changed, 1308 insertions(+), 5 deletions(-)
create mode 100644 engines/xnvme.c
create mode 100644 examples/xnvme-compare.fio
create mode 100644 examples/xnvme-zoned.fio
--
2.17.1
next parent reply other threads:[~2022-05-05 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220505132529epcas5p25512da35ba70c4eed9890f299b1db12f@epcas5p2.samsung.com>
2022-05-05 13:19 ` Ankit Kumar [this message]
[not found] ` <CGME20220505132539epcas5p41f26baadd8e697ae00f637a29f7544a1@epcas5p4.samsung.com>
2022-05-05 13:19 ` [PATCH 1/3] engines/xnvme: add xnvme engine Ankit Kumar
2022-05-06 16:55 ` Vincent Fu
[not found] ` <CGME20220505132543epcas5p21198504e47717ff87ec88a1771a6c63d@epcas5p2.samsung.com>
2022-05-05 13:19 ` [PATCH 2/3] docs: documentation for xnvme ioengine Ankit Kumar
2022-05-06 15:57 ` Vincent Fu
[not found] ` <CGME20220505132546epcas5p331f666cadd5c7e788d27d09b144e0b8a@epcas5p3.samsung.com>
2022-05-05 13:19 ` [PATCH 3/3] examples: add example job file for xnvme engine usage Ankit Kumar
2022-05-06 16:00 ` Vincent Fu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220505131935.32076-1-ankit.kumar@samsung.com \
--to=ankit.kumar@samsung.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=krish.reddy@samsung.com \
--cc=simon.lund@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.