From: Aurelien Aptel <aaptel@nvidia.com>
To: aaptel@nvidia.com, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Daniel Wagner <dwagner@suse.de>, Shai Malin <smalin@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH blktests v4 0/5] Add support to run against arbitrary targets
Date: Tue, 26 Nov 2024 22:38:51 +0200 [thread overview]
Message-ID: <20241126203857.27210-1-aaptel@nvidia.com> (raw)
This series is based off Daniel's patches. It is rebased to work on
current blktests. It is also available on github:
https://github.com/aaptel/blktests.git branch remote-target-v4
The last patch adds a test making explicit use of the remote target
support by testing the new nvme-tcp offloading.
I've added a 'blkdev' setting under [subsys_0] in the control script
config to specify the backing block device on the target, instead of
hardcoding '/dev/vdc'.
changes:
v4:
- added nvme test 055 for nvme-tcp offload
- added 'blkdev' setting under [subsys_0] in the control script config
- added workaround for older python versions
v3:
- added support for previous configured target
- renamed nvme_nvme_target to _require_kernel_nvme_target
- use shorter redirect operator
- https://lore.kernel.org/all/20240627091016.12752-1-dwagner@suse.de/
v2:
- many of the preperation patches have been merged, drop them
- added a python script which implements the blktests API
- add some documentation how to use it
- changed the casing of the environment variables to upper case
- https://lore.kernel.org/all/20240612110444.4507-1-dwagner@suse.de/
v1:
- initial version
- https://lore.kernel.org/linux-nvme/20240318093856.22307-1-dwagner@suse.de/
Aurelien Aptel (2):
common/nvme: add digest options to __nvme_connect_subsys()
nvme/055: add test for nvme-tcp zero-copy offload
Daniel Wagner (3):
nvme/rc: introduce remote target support
nvme/030: only run against kernel soft target
contrib: add remote target setup/cleanup script
Documentation/running-tests.md | 42 +++++
README.md | 1 +
check | 4 +
common/nvme | 87 +++++++++-
common/rc | 8 +
contrib/nvme_target_control.py | 190 ++++++++++++++++++++++
contrib/nvmet-subsys.jinja2 | 71 ++++++++
tests/nvme/030 | 1 +
tests/nvme/055 | 285 +++++++++++++++++++++++++++++++++
tests/nvme/055.out | 44 +++++
tests/nvme/rc | 30 ++++
11 files changed, 755 insertions(+), 8 deletions(-)
create mode 100755 contrib/nvme_target_control.py
create mode 100644 contrib/nvmet-subsys.jinja2
create mode 100755 tests/nvme/055
create mode 100644 tests/nvme/055.out
--
2.34.1
next reply other threads:[~2024-11-26 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 20:38 Aurelien Aptel [this message]
2024-11-26 20:38 ` [PATCH blktests v4 1/5] nvme/rc: introduce remote target support Aurelien Aptel
2024-11-29 10:01 ` Shinichiro Kawasaki
2024-12-02 10:23 ` Aurelien Aptel
2024-11-26 20:38 ` [PATCH blktests v4 2/5] common/nvme: add digest options to __nvme_connect_subsys() Aurelien Aptel
2024-11-26 20:38 ` [PATCH blktests v4 3/5] nvme/030: only run against kernel soft target Aurelien Aptel
2024-11-26 20:38 ` [PATCH blktests v4 4/5] contrib: add remote target setup/cleanup script Aurelien Aptel
2024-11-26 20:38 ` [PATCH blktests v4 5/5] nvme/055: add test for nvme-tcp zero-copy offload Aurelien Aptel
2024-11-29 10:20 ` Shinichiro Kawasaki
2024-12-02 10:09 ` Aurelien Aptel
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=20241126203857.27210-1-aaptel@nvidia.com \
--to=aaptel@nvidia.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 \
--cc=smalin@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.