From: Jakub Kicinski <kuba@kernel.org>
To: Gustavo Padovan <gus@collabora.com>,
"Aurelien Aptel" <aaptel@nvidia.com>
Cc: "linux-nvme" <linux-nvme@lists.infradead.org>,
"netdev" <netdev@vger.kernel.org>, "sagi" <sagi@grimberg.me>,
"hch" <hch@lst.de>, "kbusch" <kbusch@kernel.org>,
"axboe" <axboe@fb.com>, "chaitanyak" <chaitanyak@nvidia.com>,
"davem" <davem@davemloft.net>,
"aurelien.aptel" <aurelien.aptel@gmail.com>,
"smalin" <smalin@nvidia.com>, "malin1024" <malin1024@gmail.com>,
"ogerlitz" <ogerlitz@nvidia.com>, "yorayz" <yorayz@nvidia.com>,
"borisp" <borisp@nvidia.com>, "galshalom" <galshalom@nvidia.com>,
"mgurtovoy" <mgurtovoy@nvidia.com>, "tariqt" <tariqt@nvidia.com>,
"edumazet" <edumazet@google.com>
Subject: Re: [PATCH v28 00/20] nvme-tcp receive offloads
Date: Mon, 5 May 2025 13:43:34 -0700 [thread overview]
Message-ID: <20250505134334.28389275@kernel.org> (raw)
In-Reply-To: <19686c19e11.ba39875d3947402.7647787744422691035@collabora.com>
On Wed, 30 Apr 2025 09:52:38 -0300 Gustavo Padovan wrote:
> > The next iteration of our nvme-tcp receive offload series, rebased on top of
> > yesterday net-next 0d15a26b247d ("net: ti: icssg-prueth: Add ICSSG FW Stats").
> >
> > As requested, we now have CI for testing this feature. This has been
> > realized through the addition of a NIPA executor in
> > KernelCI[0]. KernelCI now has access to execute tests on the NVIDIA
> > hardware where we use this feature and then report the results for
> > NIPA collection.
> >
> > If you want, you can follow the test executions through the NIPA
> > contest page[1]. As expected, tests are failing right now as they need
> > this patchset applied to the netdev-testing hw branch, but they should
> > pass once the patches make their way in to that branch.
>
> When I go to patchwork to look for the CI results for this patchset:
>
> https://patchwork.kernel.org/project/netdevbpf/list/?series=958427&state=*
>
> No tests ran. I wonder if this is because the patches were marked as "Not applicable". [1]
> I could figure out why it was marked as Not applicable right way. My guess is that
> NIPA believes the patches should be applied elsewhere and not in net-next?
>
> Could you advise on what we need to do get this patchset through netdev-CI testing?
Looks like the tests passed? But we'll drop this from our PW, again.
Christoph Hellwig was pushing back on the v27. We can't do anything
with these until NVMe people are all happy.
The TCP changes obviously must go via the networking tree.
next prev parent reply other threads:[~2025-05-05 20:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 8:57 [PATCH v28 00/20] nvme-tcp receive offloads Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2025-05-14 7:12 ` Eric Dumazet
2025-05-16 14:47 ` Aurelien Aptel
2025-05-16 22:31 ` Jakub Kicinski
2025-05-17 7:38 ` Eric Dumazet
2025-05-22 15:01 ` Aurelien Aptel
2025-06-04 12:33 ` Aurelien Aptel
2025-06-04 12:55 ` Eric Dumazet
2025-06-05 11:54 ` Aurelien Aptel
2025-06-05 12:44 ` Eric Dumazet
2025-04-30 8:57 ` [PATCH v28 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 16/20] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 17/20] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2025-04-30 8:57 ` [PATCH v28 20/20] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2025-04-30 12:52 ` [PATCH v28 00/20] nvme-tcp receive offloads Gustavo Padovan
2025-05-05 20:43 ` Jakub Kicinski [this message]
2025-05-05 21:51 ` Keith Busch
2025-05-05 22:51 ` Jakub Kicinski
2025-05-13 12:56 ` Aurelien Aptel
2025-05-13 14:36 ` Jakub Kicinski
2025-05-06 13:34 ` Sagi Grimberg
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=20250505134334.28389275@kernel.org \
--to=kuba@kernel.org \
--cc=aaptel@nvidia.com \
--cc=aurelien.aptel@gmail.com \
--cc=axboe@fb.com \
--cc=borisp@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=galshalom@nvidia.com \
--cc=gus@collabora.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=mgurtovoy@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@nvidia.com \
--cc=sagi@grimberg.me \
--cc=smalin@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=yorayz@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;
as well as URLs for NNTP newsgroup(s).