From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Aurelien Aptel <aaptel@nvidia.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Daniel Wagner <dwagner@suse.de>, Shai Malin <smalin@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH blktests v5 1/5] nvme/rc: introduce remote target support
Date: Mon, 9 Dec 2024 07:19:26 +0000 [thread overview]
Message-ID: <68812a75-e3be-4b25-9732-e221661dbdf7@nvidia.com> (raw)
In-Reply-To: <20241206135120.5141-2-aaptel@nvidia.com>
On 12/6/24 05:51, Aurelien Aptel wrote:
> From: Daniel Wagner <dwagner@suse.de>
>
> Most of the NVMEeoF tests are exercising the host code of the nvme
> subsystem. There is no real reason not to run these against an arbitrary
> target. We just have to skip the soft target setup and make it possible
> to setup a remote target.
>
> Because all tests use now the common setup/cleanup helpers we just need
> to intercept this call and forward it to an external component.
>
> As we already have various nvme variables to setup the target which we
> should allow to overwrite. Also introduce a NVME_TARGET_CONTROL variable
> which points to a script which gets executed whenever a targets needs to
> be created/destroyed.
>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> Signed-off-by: Aurelien Aptel <aaptel@nvidia.com>
> ---
>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-12-09 7:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:51 [PATCH blktests v5 0/5] Add support to run against arbitrary targets Aurelien Aptel
2024-12-06 13:51 ` [PATCH blktests v5 1/5] nvme/rc: introduce remote target support Aurelien Aptel
2024-12-09 7:19 ` Chaitanya Kulkarni [this message]
2024-12-06 13:51 ` [PATCH blktests v5 2/5] common/nvme: add digest options to __nvme_connect_subsys() Aurelien Aptel
2024-12-09 7:19 ` Chaitanya Kulkarni
2024-12-06 13:51 ` [PATCH blktests v5 3/5] nvme/030: only run against kernel soft target Aurelien Aptel
2024-12-09 7:20 ` Chaitanya Kulkarni
2024-12-06 13:51 ` [PATCH blktests v5 4/5] contrib: add remote target setup/cleanup script Aurelien Aptel
2024-12-09 7:20 ` Chaitanya Kulkarni
2024-12-06 13:51 ` [PATCH blktests v5 5/5] nvme/055: add test for nvme-tcp zero-copy offload Aurelien Aptel
2024-12-09 7:20 ` Chaitanya Kulkarni
2026-01-28 15:28 ` John Garry
2026-01-29 2:07 ` Shinichiro Kawasaki
2026-01-29 10:28 ` Aurelien Aptel
2024-12-10 8:17 ` [PATCH blktests v5 0/5] Add support to run against arbitrary targets Shinichiro Kawasaki
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=68812a75-e3be-4b25-9732-e221661dbdf7@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=aaptel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox