From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Raed Salem <raeds@nvidia.com>
Subject: Re: [GIT PULL] Improve IPsec limits, ESN and replay window
Date: Tue, 4 Apr 2023 19:30:18 +0300 [thread overview]
Message-ID: <20230404163018.GJ4514@unreal> (raw)
In-Reply-To: <20230403064154.12443-1-leon@kernel.org>
On Mon, Apr 03, 2023 at 09:41:54AM +0300, Leon Romanovsky wrote:
> This series overcomes existing hardware limitations in Mellanox ConnectX
> devices around handling IPsec soft and hard limits.
>
> In addition, the ESN logic is tied and added an interface to configure
> replay window sequence numbers through existing iproute2 interface.
>
> ip xfrm state ... [ replay-seq SEQ ] [ replay-oseq SEQ ]
> [ replay-seq-hi SEQ ] [ replay-oseq-hi SEQ ]
>
> Link: https://lore.kernel.org/all/cover.1680162300.git.leonro@nvidia.com
> Signed-off-by: Leon Romanovsky <leon@kernel.org>
>
> ----------------------------------------------------------------
>
> The following changes since commit 5a6cddb89b51d99a7702e63829644a5860dd9c41:
>
> net/mlx5e: Update IPsec per SA packets/bytes count (2023-03-20 11:29:52 +0200)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/ tags/ipsec-esn-replay
>
> for you to fetch changes up to 9f758558e309d11ef31dbdabdb1e3aa1003aebf9:
>
> net/mlx5e: Simulate missing IPsec TX limits hardware functionality (2023-04-03 09:29:47 +0300)
>
> ----------------------------------------------------------------
> Leon Romanovsky (10):
> net/mlx5e: Factor out IPsec ASO update function
> net/mlx5e: Prevent zero IPsec soft/hard limits
> net/mlx5e: Add SW implementation to support IPsec 64 bit soft and hard limits
> net/mlx5e: Overcome slow response for first IPsec ASO WQE
> xfrm: don't require advance ESN callback for packet offload
Hi Steffen,
Can you please provide your Acked-by for this patch?
https://lore.kernel.org/all/9f3dfc3fef2cfcd191f0c5eee7cf0aa74e7f7786.1680162300.git.leonro@nvidia.com
Thanks
> net/mlx5e: Remove ESN callbacks if it is not supported
> net/mlx5e: Set IPsec replay sequence numbers
> net/mlx5e: Reduce contention in IPsec workqueue
> net/mlx5e: Generalize IPsec work structs
> net/mlx5e: Simulate missing IPsec TX limits hardware functionality
>
> .../ethernet/mellanox/mlx5/core/en_accel/ipsec.c | 329 ++++++++++++++++++---
> .../ethernet/mellanox/mlx5/core/en_accel/ipsec.h | 47 ++-
> .../mellanox/mlx5/core/en_accel/ipsec_fs.c | 31 +-
> .../mellanox/mlx5/core/en_accel/ipsec_offload.c | 198 ++++++++++---
> net/xfrm/xfrm_device.c | 2 +-
> 5 files changed, 496 insertions(+), 111 deletions(-)
prev parent reply other threads:[~2023-04-04 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 6:41 [GIT PULL] Improve IPsec limits, ESN and replay window Leon Romanovsky
2023-04-04 16:30 ` Leon Romanovsky [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=20230404163018.GJ4514@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raeds@nvidia.com \
--cc=saeedm@nvidia.com \
--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).