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, edumazet@google.com
Subject: Re: [PATCH v18 00/20] nvme-tcp receive offloads
Date: Sun, 29 Oct 2023 23:15:33 -0700 [thread overview]
Message-ID: <20231029231533.79dcb9ef@kernel.org> (raw)
In-Reply-To: <20231027122755.205334-1-aaptel@nvidia.com>
On Fri, 27 Oct 2023 12:27:35 +0000 Aurelien Aptel wrote:
> The next iteration of our nvme-tcp receive offload series.
> The main change is the move of the capabilities from the netdev to the driver.
Patches 15-17 never made it to the list :(
Please note that net-next is closed for the duration of the merge
window.
--
pw-bot: cr
prev parent reply other threads:[~2023-10-30 6:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 12:27 [PATCH v18 00/20] nvme-tcp receive offloads Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-10-27 12:27 ` [PATCH v18 20/20] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
2023-10-30 6:15 ` 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=20231029231533.79dcb9ef@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=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.