From: Guixin Liu <kanie@linux.alibaba.com>
To: shinichiro.kawasaki@wdc.com
Cc: chaitanyak@nvidia.com, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: [PATCH V2 0/2] *** Test the NVMe reservation feature ***
Date: Wed, 17 Jan 2024 16:17:40 +0800 [thread overview]
Message-ID: <20240117081742.93941-1-kanie@linux.alibaba.com> (raw)
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/{rc,002,016,017,030,031}: introduce --resv_enable argument
test/nvme/050: test the reservation feature
tests/nvme/002 | 3 +-
tests/nvme/016 | 7 ++-
tests/nvme/017 | 10 +++--
tests/nvme/030 | 6 ++-
tests/nvme/031 | 3 +-
tests/nvme/050 | 96 ++++++++++++++++++++++++++++++++++++++++
tests/nvme/050.out | 108 +++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/rc | 100 ++++++++++++++++++++++++++++++++++-------
8 files changed, 308 insertions(+), 25 deletions(-)
create mode 100644 tests/nvme/050
create mode 100644 tests/nvme/050.out
--
2.30.1 (Apple Git-130)
next reply other threads:[~2024-01-17 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 8:17 Guixin Liu [this message]
2024-01-17 8:17 ` [PATCH V2 1/2] nvme/{rc,002,016,017,030,031}: introduce --resv_enable argument Guixin Liu
2024-01-23 10:54 ` Shinichiro Kawasaki
2024-01-31 14:47 ` Daniel Wagner
2024-01-17 8:17 ` [PATCH V2 2/2] test/nvme/050: test the reservation feature Guixin Liu
2024-01-23 11:21 ` Shinichiro Kawasaki
2024-01-23 11:41 ` 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=20240117081742.93941-1-kanie@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=chaitanyak@nvidia.com \
--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