From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Jianbo Liu <jianbol@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Potnuri Bharat Teja <bharat@chelsio.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH ipsec-next 1/2] xfrm: Support ESN context update to hardware for TX
Date: Tue, 7 Jan 2025 14:09:05 +0200 [thread overview]
Message-ID: <20250107120905.GD87447@unreal> (raw)
In-Reply-To: <Z30WcStdG5Z4tDru@gauss3.secunet.de>
On Tue, Jan 07, 2025 at 12:56:33PM +0100, Steffen Klassert wrote:
> On Tue, Jan 07, 2025 at 12:22:04PM +0200, Leon Romanovsky wrote:
> > On Thu, Dec 19, 2024 at 02:37:29PM +0200, Leon Romanovsky wrote:
> > > From: Jianbo Liu <jianbol@nvidia.com>
> > >
> > > Previously xfrm_dev_state_advance_esn() was added for RX only. But
> > > it's possible that ESN context also need to be synced to hardware for
> > > TX, so call it for outbound in this patch.
> > >
> > > Signed-off-by: Jianbo Liu <jianbol@nvidia.com>
> > > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > > ---
> > > Documentation/networking/xfrm_device.rst | 3 ++-
> > > drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 3 +++
> > > drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c | 3 +++
> > > net/xfrm/xfrm_replay.c | 1 +
> > > 4 files changed, 9 insertions(+), 1 deletion(-)
> >
> > Steffen,
> >
> > This is kindly reminder.
>
> Sorry for the dealy, the holidays came faster than expected :)
>
> > > diff --git a/net/xfrm/xfrm_replay.c b/net/xfrm/xfrm_replay.c
> > > index bc56c6305725..e500aebbad22 100644
> > > --- a/net/xfrm/xfrm_replay.c
> > > +++ b/net/xfrm/xfrm_replay.c
> > > @@ -729,6 +729,7 @@ static int xfrm_replay_overflow_offload_esn(struct xfrm_state *x, struct sk_buff
> > > }
> > >
> > > replay_esn->oseq = oseq;
> > > + xfrm_dev_state_advance_esn(x);
>
> This is the only line of code that this patchset adds
> to the xfrm stack, so merging this through mlx5 might
> create less conflicts.
>
> In case you want to do that, you can add my 'Acked-by'
> to this patch. Otherwise I'll pull it into the ipsec-next
> tree tomorrow.
Let's do it through your tree, please. IMHO, it is more appropriate.
Thanks
next prev parent reply other threads:[~2025-01-07 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 12:37 [PATCH ipsec-next 1/2] xfrm: Support ESN context update to hardware for TX Leon Romanovsky
2024-12-19 12:37 ` [PATCH ipsec-next 2/2] net/mlx5e: Update TX ESN context for IPSec hardware offload Leon Romanovsky
2025-01-07 10:22 ` [PATCH ipsec-next 1/2] xfrm: Support ESN context update to hardware for TX Leon Romanovsky
2025-01-07 11:56 ` Steffen Klassert
2025-01-07 12:09 ` Leon Romanovsky [this message]
2025-01-08 10:25 ` 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=20250107120905.GD87447@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bharat@chelsio.com \
--cc=corbet@lwn.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=steffen.klassert@secunet.com \
--cc=tariqt@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 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).