From: Luis Chamberlain <mcgrof@kernel.org>
To: osandov@fb.com, mcgrof@kernel.org
Cc: joshi.k@samsung.com, j.granados@samsung.com,
anuj20.g@samsung.com, ankit.kumar@samsung.com,
vincent.fu@samsung.com, ming.lei@redhat.com,
linux-block@vger.kernel.org
Subject: [PATCH 0/6] blktests: char device tests with iouring-cmd fio
Date: Wed, 21 Dec 2022 02:34:35 -0800 [thread overview]
Message-ID: <20221221103441.3216600-1-mcgrof@kernel.org> (raw)
As io-uring cmd grows there's a desire to do a bit more funky things
with it. Add basic support with fio and add a few simple tests to
tests the NVMe conventional drives character device as well as the
ZNS character device.
These tests are perhaps a bit *too* basic to merge, not sure, let
me know. But I figured that this would provide example to let us
grow this with more complex things later as folks add support for
more features.
Luis Chamberlain (6):
common/fio: add helpers using io-uring cmd engine
tests/nvme: add new test for rand-read on the nvme character device
tests/nvme: add new test for rand-write on the nvme character device
tests/nvme: add new test for optimal write on the nvme character
device
tests/zbd: add new basic test for reading zone character device
tests/zbd: add new basic test for reading zone character device
common/fio | 47 +++++++++++++++++++++++++++++++++++++++++
tests/nvme/046 | 42 +++++++++++++++++++++++++++++++++++++
tests/nvme/046.out | 2 ++
tests/nvme/047 | 41 ++++++++++++++++++++++++++++++++++++
tests/nvme/047.out | 2 ++
tests/nvme/048 | 41 ++++++++++++++++++++++++++++++++++++
tests/nvme/048.out | 2 ++
tests/zbd/011 | 52 ++++++++++++++++++++++++++++++++++++++++++++++
tests/zbd/011.out | 2 ++
tests/zbd/012 | 50 ++++++++++++++++++++++++++++++++++++++++++++
tests/zbd/012.out | 2 ++
11 files changed, 283 insertions(+)
create mode 100755 tests/nvme/046
create mode 100644 tests/nvme/046.out
create mode 100755 tests/nvme/047
create mode 100644 tests/nvme/047.out
create mode 100755 tests/nvme/048
create mode 100644 tests/nvme/048.out
create mode 100755 tests/zbd/011
create mode 100644 tests/zbd/011.out
create mode 100755 tests/zbd/012
create mode 100644 tests/zbd/012.out
--
2.35.1
next reply other threads:[~2022-12-21 10:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:34 Luis Chamberlain [this message]
2022-12-21 10:34 ` [PATCH 1/6] common/fio: add helpers using io-uring cmd engine Luis Chamberlain
2022-12-30 10:10 ` Joel Granados
2022-12-21 10:34 ` [PATCH 2/6] tests/nvme: add new test for rand-read on the nvme character device Luis Chamberlain
2022-12-23 13:11 ` Kanchan Joshi
2022-12-23 15:56 ` Luis Chamberlain
2023-01-17 7:46 ` Kanchan Joshi
2022-12-30 10:37 ` Joel Granados
2023-01-03 5:48 ` Chaitanya Kulkarni
2022-12-21 10:34 ` [PATCH 3/6] tests/nvme: add new test for rand-write " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 4/6] tests/nvme: add new test for optimal write " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 5/6] tests/zbd: add new basic test for reading zone " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 6/6] " Luis Chamberlain
2022-12-28 3:25 ` [PATCH 0/6] blktests: char device tests with iouring-cmd fio Shinichiro Kawasaki
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=20221221103441.3216600-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=ankit.kumar@samsung.com \
--cc=anuj20.g@samsung.com \
--cc=j.granados@samsung.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=vincent.fu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).