From: Steffen Klassert <steffen.klassert@secunet.com>
To: Antony Antony <antony.antony@secunet.com>
Cc: Eyal Birger <eyal.birger@gmail.com>, <davem@davemloft.net>,
<dsahern@kernel.org>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <herbert@gondor.apana.org.au>,
<pablo@netfilter.org>, <paul.wouters@aiven.io>,
<nharold@google.com>, <mcr@sandelman.ca>, <devel@linux-ipsec.org>,
<netdev@vger.kernel.org>
Subject: Re: [devel-ipsec] [PATCH ipsec-next, v4] xfrm: support sending NAT keepalives in ESP in UDP states
Date: Thu, 27 Jun 2024 12:01:56 +0200 [thread overview]
Message-ID: <Zn04lL533UFXpvYZ@gauss3.secunet.de> (raw)
In-Reply-To: <ZnqaKO2Mz/ZR6sNT@moon.secunet.de>
On Tue, Jun 25, 2024 at 12:21:28PM +0200, Antony Antony wrote:
> On Mon, May 27, 2024 at 20:29:14 -0700, Eyal Birger via Devel wrote:
> > Add the ability to send out RFC-3948 NAT keepalives from the xfrm stack.
> >
> > To use, Userspace sets an XFRM_NAT_KEEPALIVE_INTERVAL integer property when
> > creating XFRM outbound states which denotes the number of seconds between
> > keepalive messages.
> >
> > Keepalive messages are sent from a per net delayed work which iterates over
> > the xfrm states. The logic is guarded by the xfrm state spinlock due to the
> > xfrm state walk iterator.
> >
> > Possible future enhancements:
> >
> > - Adding counters to keep track of sent keepalives.
> > - deduplicate NAT keepalives between states sharing the same nat keepalive
> > parameters.
> > - provisioning hardware offloads for devices capable of implementing this.
> > - revise xfrm state list to use an rcu list in order to avoid running this
> > under spinlock.
> >
> > Suggested-by: Paul Wouters <paul.wouters@aiven.io>
> > Signed-off-by: Eyal Birger <eyal.birger@gmail.com>
>
> Tested-by: Antony Antony <antony.antony@secunet.com>
Now applied to ipsec-next, thanks everyone!
prev parent reply other threads:[~2024-06-27 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 3:29 [PATCH ipsec-next,v4] xfrm: support sending NAT keepalives in ESP in UDP states Eyal Birger
2024-05-31 7:10 ` Steffen Klassert
2024-06-11 5:45 ` Antony Antony
2024-06-11 17:07 ` Eyal Birger
[not found] ` <CAGL5yWb8Npve9wyB2WrKxAQANAa53ritU4JLzhTHV_eXppkCHg@mail.gmail.com>
2024-06-11 18:22 ` Eyal Birger
2024-06-25 10:21 ` [devel-ipsec] [PATCH ipsec-next, v4] " Antony Antony
2024-06-27 10:01 ` Steffen Klassert [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=Zn04lL533UFXpvYZ@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=antony.antony@secunet.com \
--cc=davem@davemloft.net \
--cc=devel@linux-ipsec.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=mcr@sandelman.ca \
--cc=netdev@vger.kernel.org \
--cc=nharold@google.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=paul.wouters@aiven.io \
/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