From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: John Garry <john.g.garry@oracle.com>
Cc: 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>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Daniel Wagner <dwagner@suse.de>, Shai Malin <smalin@nvidia.com>
Subject: Re: [PATCH blktests v5 5/5] nvme/055: add test for nvme-tcp zero-copy offload
Date: Thu, 29 Jan 2026 02:07:17 +0000 [thread overview]
Message-ID: <aXq7nHT2FGEIQn7B@shinmob> (raw)
In-Reply-To: <a19ae203-bda9-4034-a1f0-7528e942d7d4@oracle.com>
On Jan 28, 2026 / 15:28, John Garry wrote:
> On 06/12/2024 13:51, Aurelien Aptel wrote:
> > +++ b/tests/nvme/055
> > @@ -0,0 +1,268 @@
> > +#!/bin/bash
> > +# SPDX-License-Identifier: GPL-3.0+
> > +# Copyright (C) 2024 Aurelien Aptel<aaptel@nvidia.com>
> > +#
> > +# zero-copy offload
> > +
> > +. tests/nvme/rc
> > +
> > +DESCRIPTION="enable zero copy offload and run rw traffic"
> > +TIMED=1
> > +
> > +iface_idx=""
> > +
> > +# these vars get updated after each call to connect_run_disconnect()
> > +nb_packets=0
> > +nb_bytes=0
> > +nb_offload_packets=0
> > +nb_offload_bytes=0
> > +offload_bytes_ratio=0
> > +offload_packets_ratio=0
> > +
> > +requires() {
> > + _nvme_requires
> > + _require_remote_nvme_target
> > + _require_nvme_trtype tcp
> > + _have_kernel_option ULP_DDP
>
> I notice that this kernel config option is still not included in mainline,
> over 1 year later.
>
> It is strange to me to merge tests for features which are yet to be
> accepted.
When this test case was added, I was aware of that the DDP offload feature was
not yet accepted [1]. At that time, I expected that the feature would be applied
soon.
This test case was the first use case of the blktests feature
"NVME_TARGET_CONTROL" which allows setting up nvme targets for testing in
flexible manner [2]. The test case was useful to demonstrate the value of the
feature. That's why I merged the test for "features which are yet to be
accepted".
Said that, assuming the DDP offload feature is not going to be mainlined, this
test case has lost its value. I think it is reasonable to remove the test case
at this moment. A patch post for removal will be helpful to confirm consensus.
[1] https://lore.kernel.org/all/2537c8iv1kq.fsf@nvidia.com/
[2] https://lore.kernel.org/linux-block/20241206135120.5141-2-aaptel@nvidia.com/
next prev parent reply other threads:[~2026-01-29 2:07 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
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 [this message]
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=aXq7nHT2FGEIQn7B@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=aaptel@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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