From: Leon Romanovsky <leonro@nvidia.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"Jakub Kicinski" <kuba@kernel.org>, <netdev@vger.kernel.org>,
Bharat Bhushan <bbhushan2@marvell.com>
Subject: Re: [PATCH xfrm-next 00/13] mlx5 IPsec packet offload support (Part I)
Date: Fri, 2 Dec 2022 22:19:33 +0200 [thread overview]
Message-ID: <Y4pd1ZrFXizV5TqF@unreal> (raw)
In-Reply-To: <cover.1670011885.git.leonro@nvidia.com>
On Fri, Dec 02, 2022 at 10:14:44PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> This is second part with implementation of packet offload.
The title is misleading, it should be written "Part II".
Sorry for that.
Thanks
next prev parent reply other threads:[~2022-12-02 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 20:14 [PATCH xfrm-next 00/13] mlx5 IPsec packet offload support (Part I) Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 01/13] net/mlx5e: Create IPsec policy offload tables Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 02/13] net/mlx5e: Add XFRM policy offload logic Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 03/13] net/mlx5e: Use same coding pattern for Rx and Tx flows Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 04/13] net/mlx5e: Configure IPsec packet offload flow steering Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 05/13] net/mlx5e: Improve IPsec flow steering autogroup Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 06/13] net/mlx5e: Add statistics for Rx/Tx IPsec offloaded flows Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 07/13] net/mlx5e: Skip IPsec encryption for TX path without matching policy Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 08/13] net/mlx5e: Provide intermediate pointer to access IPsec struct Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 09/13] net/mlx5e: Store all XFRM SAs in Xarray Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 10/13] net/mlx5e: Update IPsec soft and hard limits Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 11/13] net/mlx5e: Handle hardware IPsec limits events Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 12/13] net/mlx5e: Handle ESN update events Leon Romanovsky
2022-12-02 20:14 ` [PATCH xfrm-next 13/13] net/mlx5e: Open mlx5 driver to accept IPsec packet offload Leon Romanovsky
2022-12-02 20:19 ` Leon Romanovsky [this message]
2022-12-09 7:18 ` [PATCH xfrm-next 00/13] mlx5 IPsec packet offload support (Part I) Steffen Klassert
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=Y4pd1ZrFXizV5TqF@unreal \
--to=leonro@nvidia.com \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).