public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "osandov@fb.com" <osandov@fb.com>,
	"joshi.k@samsung.com" <joshi.k@samsung.com>,
	"j.granados@samsung.com" <j.granados@samsung.com>,
	"anuj20.g@samsung.com" <anuj20.g@samsung.com>,
	"ankit.kumar@samsung.com" <ankit.kumar@samsung.com>,
	"vincent.fu@samsung.com" <vincent.fu@samsung.com>,
	"ming.lei@redhat.com" <ming.lei@redhat.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 0/6] blktests: char device tests with iouring-cmd fio
Date: Wed, 28 Dec 2022 03:25:42 +0000	[thread overview]
Message-ID: <20221228032540.lkprcp64numwjvr7@shindev> (raw)
In-Reply-To: <20221221103441.3216600-1-mcgrof@kernel.org>

On Dec 21, 2022 / 02:34, Luis Chamberlain wrote:
> 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.

It is good to have new test cases to test new features and their new code paths.
I agree to have new test cases for the NVMe character device with io-uring.

Having said that, I'm not sure if we should have all of the five test cases in
the series. The test cases nvme/046, 047, 048 are similar. They do random read,
random write, or sequential write respectively. I'm not sure how the workload
difference expands the code coverage of the code paths in the NVMe driver. Same
for zbd/011 and 012. They are intended for ZNS devices, but I do not see ZNS
unique part in the NVMe character device code paths. Then the variation of the
test cases do not look useful to find bugs in the driver. As the first step, I
think single test case will be enough which does basic read and/or write to
exercises the NVMe character device and io-uring.

-- 
Shin'ichiro Kawasaki

      parent reply	other threads:[~2022-12-28  3:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 10:34 [PATCH 0/6] blktests: char device tests with iouring-cmd fio Luis Chamberlain
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 ` Shinichiro Kawasaki [this message]

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=20221228032540.lkprcp64numwjvr7@shindev \
    --to=shinichiro.kawasaki@wdc.com \
    --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=mcgrof@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