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 v16 00/20] nvme-tcp receive offloads
Date: Fri, 13 Oct 2023 08:49:42 -0700 [thread overview]
Message-ID: <20231013084942.4ddc2b90@kernel.org> (raw)
In-Reply-To: <20230928150954.1684-1-aaptel@nvidia.com>
On Thu, 28 Sep 2023 15:09:34 +0000 Aurelien Aptel wrote:
> The next iteration of our nvme-tcp receive offload series.
> This submission was rebased on top of net-next.
>
> Previous submission (v15):
> https://lore.kernel.org/netdev/d761c2de-fea3-cbd0-ced8-cee91a670552@grimberg.me/T/
>
> The changes are also available through git:
> Repo: https://github.com/aaptel/linux.git branch nvme-rx-offload-v16
> Web: https://github.com/aaptel/linux/tree/nvme-rx-offload-v16
>
> The NVMe-TCP offload was presented in netdev 0x16 (video available):
> - https://netdevconf.info/0x16/session.html?NVMeTCP-Offload-%E2%80%93-Implementation-and-Performance-Gains
> - https://youtu.be/W74TR-SNgi4
FTR you need an explicit Ack from Eric on the TCP and skb parts.
prev parent reply other threads:[~2023-10-13 15:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 15:09 [PATCH v16 00/20] nvme-tcp receive offloads Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 16/20] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 17/20] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-09-28 15:09 ` [PATCH v16 20/20] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2023-10-13 15:49 ` 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=20231013084942.4ddc2b90@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 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.