From: Guixin Liu <kanie@linux.alibaba.com>
To: shinichiro.kawasaki@wdc.com, dwagner@suse.de, chaitanyak@nvidia.com
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: [PATCH blktests v4 0/2] Test the NVMe reservation feature
Date: Mon, 14 Oct 2024 17:01:14 +0800 [thread overview]
Message-ID: <20241014090116.125500-1-kanie@linux.alibaba.com> (raw)
Changes from v3 to v4:
- Introduce var test_dev="/dev/${nvmedev}n1" instead of using
"/dev/${nvmedev}n1" everywhere.
- Filter the resv-report result.
Changes from v2 to v3:
- Put calling "resv-report --help" to the beginning of test_resv().
- Introduce a hlper resv_report.
- Fit newest blktests version.
Changes from v1 to v2:
- Add a new patch to add a optinal argument --resv_enable.
- Make resv-report fit the new --eds argument.
- Filter the hosid output to make the new test case independent from
hostid.
- Change the new test case name to "Test the NVMe reservation feature".
Guixin Liu (2):
nvme/{md/001,rc,002,016,017,030,052}: introduce --resv_enable argument
nvme: test the nvme reservation feature
common/nvme | 89 +++++++++++++++++++++++++++++++++------
tests/md/001 | 4 +-
tests/nvme/002 | 3 +-
tests/nvme/016 | 7 +++-
tests/nvme/017 | 10 +++--
tests/nvme/030 | 6 ++-
tests/nvme/052 | 5 ++-
tests/nvme/054 | 101 +++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/054.out | 68 ++++++++++++++++++++++++++++++
tests/nvme/rc | 11 ++++-
10 files changed, 278 insertions(+), 26 deletions(-)
create mode 100644 tests/nvme/054
create mode 100644 tests/nvme/054.out
--
2.43.0
next reply other threads:[~2024-10-14 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 9:01 Guixin Liu [this message]
2024-10-14 9:01 ` [PATCH blktests v4 1/2] nvme/{md/001,rc,002,016,017,030,052}: introduce --resv_enable argument Guixin Liu
2024-10-14 9:01 ` [PATCH blktests v4 2/2] nvme: test the nvme reservation feature Guixin Liu
2024-10-14 11:44 ` Daniel Wagner
2024-10-15 1:19 ` Guixin Liu
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=20241014090116.125500-1-kanie@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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