From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
saeedm@nvidia.com, raeds@nvidia.com
Subject: Re: [GIT PULL v1] Improve IPsec limits, ESN and replay window
Date: Sat, 08 Apr 2023 03:10:20 +0000 [thread overview]
Message-ID: <168092342002.22423.485223944189178908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230406071902.712388-1-leon@kernel.org>
Hello:
This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Apr 2023 10:19:02 +0300 you 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 ]
>
> [...]
Here is the summary with links:
- [GIT,PULL,v1] Improve IPsec limits, ESN and replay window
https://git.kernel.org/netdev/net-next/c/4bcdfc3ab217
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-08 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 7:19 [GIT PULL v1] Improve IPsec limits, ESN and replay window Leon Romanovsky
2023-04-07 19:01 ` Leon Romanovsky
2023-04-08 3:10 ` patchwork-bot+netdevbpf [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=168092342002.22423.485223944189178908.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=leon@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 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.