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 2/2] test/nvme/050: test the reservation feature
Date: Wed, 17 Jan 2024 16:17:42 +0800 [thread overview]
Message-ID: <20240117081742.93941-3-kanie@linux.alibaba.com> (raw)
In-Reply-To: <20240117081742.93941-1-kanie@linux.alibaba.com>
Test the reservation feature, includes register, acquire, release
and report.
Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
---
tests/nvme/050 | 96 ++++++++++++++++++++++++++++++++++++++++
tests/nvme/050.out | 108 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 204 insertions(+)
create mode 100644 tests/nvme/050
create mode 100644 tests/nvme/050.out
diff --git a/tests/nvme/050 b/tests/nvme/050
new file mode 100644
index 0000000..7e59de4
--- /dev/null
+++ b/tests/nvme/050
@@ -0,0 +1,96 @@
+#!/bin/bash
+# SPDX-License-Identifier: GPL-3.0+
+# Copyright (C) 2024 Guixin Liu
+# Copyright (C) 2024 Alibaba Group.
+#
+# Test the NVMe reservation feature
+#
+. tests/nvme/rc
+
+DESCRIPTION="test the reservation feature"
+QUICK=1
+
+requires() {
+ _nvme_requires
+}
+
+resv_report() {
+ local nvmedev=$1
+
+ if nvme resv-report --help 2>&1 | grep -- '--eds' > /dev/null; then
+ nvme resv-report "/dev/${nvmedev}n1" --eds | grep -v "hostid"
+ else
+ nvme resv-report "/dev/${nvmedev}n1" --cdw11=1 | grep -v "hostid"
+ fi
+}
+
+test_resv() {
+ local nvmedev=$1
+
+ echo "Register"
+ resv_report "${nvmedev}"
+ nvme resv-register "/dev/${nvmedev}n1" --nrkey=4 --rrega=0
+ resv_report "${nvmedev}"
+
+ echo "Replace"
+ nvme resv-register "/dev/${nvmedev}n1" --crkey=4 --nrkey=5 --rrega=2
+ resv_report "${nvmedev}"
+
+ echo "Unregister"
+ nvme resv-register "/dev/${nvmedev}n1" --crkey=5 --rrega=1
+ resv_report "${nvmedev}"
+
+ echo "Acquire"
+ nvme resv-register "/dev/${nvmedev}n1" --nrkey=4 --rrega=0
+ nvme resv-acquire "/dev/${nvmedev}n1" --crkey=4 --rtype=1 --racqa=0
+ resv_report "${nvmedev}"
+
+ echo "Preempt"
+ nvme resv-acquire "/dev/${nvmedev}n1" --crkey=4 --rtype=2 --racqa=1
+ resv_report "${nvmedev}"
+
+ echo "Release"
+ nvme resv-release "/dev/${nvmedev}n1" --crkey=4 --rtype=2 --rrela=0
+ resv_report "${nvmedev}"
+
+ echo "Clear"
+ nvme resv-register "/dev/${nvmedev}n1" --nrkey=4 --rrega=0
+ nvme resv-acquire "/dev/${nvmedev}n1" --crkey=4 --rtype=1 --racqa=0
+ resv_report "${nvmedev}"
+ nvme resv-release "/dev/${nvmedev}n1" --crkey=4 --rrela=1
+}
+
+test() {
+ echo "Running ${TEST_NAME}"
+
+ _setup_nvmet
+
+ local nvmedev
+ local skipped=false
+ local subsys_path=""
+ local ns_path=""
+
+ _nvmet_target_setup --blkdev file --resv_enable
+ subsys_path="${NVMET_CFS}/subsystems/${def_subsysnqn}"
+ ns_path="${subsys_path}/namespaces/1"
+
+ if [[ -f "${ns_path}/resv_enable" ]] ; then
+ _nvme_connect_subsys "${nvme_trtype}" "${def_subsysnqn}"
+
+ nvmedev=$(_find_nvme_dev "${def_subsysnqn}")
+
+ test_resv "${nvmedev}"
+ _nvme_disconnect_subsys "${def_subsysnqn}"
+ else
+ SKIP_REASONS+=("missing reservation feature")
+ skipped=true
+ fi
+
+ _nvmet_target_cleanup
+
+ if [[ "${skipped}" = true ]] ; then
+ return 1
+ fi
+
+ echo "Test complete"
+}
diff --git a/tests/nvme/050.out b/tests/nvme/050.out
new file mode 100644
index 0000000..2a46b32
--- /dev/null
+++ b/tests/nvme/050.out
@@ -0,0 +1,108 @@
+Running nvme/050
+Register
+
+NVME Reservation status:
+
+gen : 0
+rtype : 0
+regctl : 0
+ptpls : 0
+
+NVME Reservation success
+
+NVME Reservation status:
+
+gen : 1
+rtype : 0
+regctl : 1
+ptpls : 0
+regctlext[0] :
+ cntlid : 1
+ rcsts : 0
+ rkey : 4
+
+Replace
+NVME Reservation success
+
+NVME Reservation status:
+
+gen : 2
+rtype : 0
+regctl : 1
+ptpls : 0
+regctlext[0] :
+ cntlid : 1
+ rcsts : 0
+ rkey : 5
+
+Unregister
+NVME Reservation success
+
+NVME Reservation status:
+
+gen : 3
+rtype : 0
+regctl : 0
+ptpls : 0
+
+Acquire
+NVME Reservation success
+NVME Reservation Acquire success
+
+NVME Reservation status:
+
+gen : 4
+rtype : 1
+regctl : 1
+ptpls : 0
+regctlext[0] :
+ cntlid : 1
+ rcsts : 1
+ rkey : 4
+
+Preempt
+NVME Reservation Acquire success
+
+NVME Reservation status:
+
+gen : 5
+rtype : 2
+regctl : 1
+ptpls : 0
+regctlext[0] :
+ cntlid : 1
+ rcsts : 1
+ rkey : 4
+
+Release
+NVME Reservation Release success
+
+NVME Reservation status:
+
+gen : 5
+rtype : 0
+regctl : 1
+ptpls : 0
+regctlext[0] :
+ cntlid : 1
+ rcsts : 0
+ rkey : 4
+
+Clear
+NVME Reservation success
+NVME Reservation Acquire success
+
+NVME Reservation status:
+
+gen : 6
+rtype : 1
+regctl : 1
+ptpls : 0
+regctlext[0] :
+ cntlid : 1
+ rcsts : 1
+ rkey : 4
+
+NVME Reservation Release success
+disconnected 1 controller(s)
+Test complete
--
2.30.1 (Apple Git-130)
next prev parent reply other threads:[~2024-01-17 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 8:17 [PATCH V2 0/2] *** Test the NVMe reservation feature *** Guixin Liu
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 ` Guixin Liu [this message]
2024-01-23 11:21 ` [PATCH V2 2/2] test/nvme/050: test the reservation feature 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-3-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