From: Jakub Kicinski <kuba@kernel.org>
To: Aurelien Aptel <aaptel@nvidia.com>
Cc: linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
sagi@grimberg.me, hch@lst.de, kbusch@kernel.org, axboe@fb.com,
chaitanyak@nvidia.com, davem@davemloft.net,
aurelien.aptel@gmail.com, smalin@nvidia.com, malin1024@gmail.com,
ogerlitz@nvidia.com, yorayz@nvidia.com, borisp@nvidia.com,
galshalom@nvidia.com, mgurtovoy@nvidia.com
Subject: Re: [PATCH v13 00/24] nvme-tcp receive offloads
Date: Wed, 23 Aug 2023 19:02:25 -0700 [thread overview]
Message-ID: <20230823190225.5688f1ad@kernel.org> (raw)
In-Reply-To: <20230822150425.3390-1-aaptel@nvidia.com>
On Tue, 22 Aug 2023 15:04:01 +0000 Aurelien Aptel wrote:
> The next iteration of our nvme-tcp receive offload series.
> This submission was rebased on top of net-next, and on top of
> the NVMe-TCP TLS implementation v10.
> https://lore.kernel.org/all/20230816120608.37135-1-hare@suse.de/
Please post as RFC if there are dependencies, we can't apply this,
anyway.
More importantly it took so long to revise this series we had made
significant progress with the netlink infra. I think you should move
out from ethtool into a dedicated family, in a similar fashion to:
https://github.com/kuba-moo/linux/tree/psp
prev parent reply other threads:[~2023-08-24 2:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 15:04 [PATCH v13 00/24] nvme-tcp receive offloads Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 01/24] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 02/24] net/ethtool: add new stringset ETH_SS_ULP_DDP_{CAPS,STATS} Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 03/24] net/ethtool: add ULP_DDP_{GET,SET} operations for caps and stats Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 04/24] Documentation: document netlink ULP_DDP_GET/SET messages Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 05/24] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 06/24] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 07/24] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 08/24] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 09/24] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 10/24] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 11/24] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 12/24] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 13/24] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 14/24] net/mlx5e: Have mdev pointer directly on the icosq structure Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 15/24] net/mlx5e: Refactor doorbell function to allow avoiding a completion Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 16/24] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 17/24] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 18/24] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 19/24] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 20/24] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 21/24] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 22/24] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 23/24] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-08-22 15:04 ` [PATCH v13 24/24] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2023-08-24 2:02 ` Jakub Kicinski [this message]
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=20230823190225.5688f1ad@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=galshalom@nvidia.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=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).