From: Daniel Wagner <dwagner@suse.de>
To: linux-block@vger.kernel.org
Cc: linux-nvme@lists.infradead.org,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Sagi Grimberg <sagi@grimberg.me>, Hannes Reinecke <hare@suse.de>,
James Smart <jsmart2021@gmail.com>,
Daniel Wagner <dwagner@suse.de>
Subject: [PATCH blktests v5 0/4] test queue count changes on reconnect
Date: Wed, 5 Apr 2023 17:46:26 +0200 [thread overview]
Message-ID: <20230405154630.16298-1-dwagner@suse.de> (raw)
The target is allowed to change the number of i/o queues. test if the
host is able to reconnect in this scenario.
I was able to test this successfully with tcp and rdma. fc still fails due to
the race condition in the target code.
Next attempt to get this series upstream :)
This version is based on my previous posted nvme/047 patches [1]
[1] https://lore.kernel.org/linux-nvme/20230329090202.8351-1-dwagner@suse.de/
v5:
- moved generic parts to nvme/rc
- renamed test to 048
- rebased ontop of nvme/047
v4:
- do not remove ports instead depend on host removing
controllers, see
https://lore.kernel.org/linux-nvme/20220927143157.3659-1-dwagner@suse.de/
- https://lore.kernel.org/linux-nvme/20220927143719.4214-1-dwagner@suse.de/
v3:
- Added comment why at least 2 CPUs are needed for the test
- Fixed shell quoting in _set_nvmet_attr_qid_max
- https://lore.kernel.org/linux-nvme/20220913065758.134668-1-dwagner@suse.de/
v2:
- detect if attr_qid_max is available
- https://lore.kernel.org/linux-block/20220831153506.28234-1-dwagner@suse.de/
v1:
- https://lore.kernel.org/linux-block/20220831120900.13129-1-dwagner@suse.de/
Daniel Wagner (4):
nvme/rc: Add setter for attr_qid_max
nvme/rc: Add nvmet attribute feature detection function
nvme/rc: Add helper to wait for nvme ctrl state
nvme/048: test queue count changes on reconnect
tests/nvme/048 | 81 ++++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/048.out | 3 ++
tests/nvme/rc | 58 +++++++++++++++++++++++++++++++++
3 files changed, 142 insertions(+)
create mode 100755 tests/nvme/048
create mode 100644 tests/nvme/048.out
--
2.40.0
next reply other threads:[~2023-04-05 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 15:46 Daniel Wagner [this message]
2023-04-05 15:46 ` [PATCH blktests v5 1/4] nvme/rc: Add setter for attr_qid_max Daniel Wagner
2023-04-05 18:39 ` Chaitanya Kulkarni
2023-04-06 6:12 ` Daniel Wagner
2023-04-06 7:05 ` Chaitanya Kulkarni
2023-04-06 7:32 ` Daniel Wagner
2023-04-05 15:46 ` [PATCH blktests v5 2/4] nvme/rc: Add nvmet attribute feature detection function Daniel Wagner
2023-04-05 15:46 ` [PATCH blktests v5 3/4] nvme/rc: Add helper to wait for nvme ctrl state Daniel Wagner
2023-04-05 18:43 ` Chaitanya Kulkarni
2023-04-05 15:46 ` [PATCH blktests v5 4/4] nvme/048: test queue count changes on reconnect Daniel Wagner
2023-04-05 18:44 ` Chaitanya Kulkarni
2023-04-05 18:57 ` Chaitanya Kulkarni
2023-04-06 6:17 ` Daniel Wagner
2023-04-06 7:04 ` Chaitanya Kulkarni
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=20230405154630.16298-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=hare@suse.de \
--cc=jsmart2021@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--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