From: Jakub Kicinski <kuba@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Tobias Brunner <tobias@strongswan.org>,
Antony Antony <antony.antony@secunet.com>,
Daniel Xu <dxu@dxuuu.xyz>, Paul Wouters <paul@nohats.ca>,
Simon Horman <horms@kernel.org>,
Sabrina Dubroca <sd@queasysnail.net>, <netdev@vger.kernel.org>,
<devel@linux-ipsec.org>
Subject: Re: [PATCH 2/4] xfrm: Cache used outbound xfrm states at the policy.
Date: Mon, 7 Oct 2024 07:26:23 -0700 [thread overview]
Message-ID: <20241007072623.1b7b24f9@kernel.org> (raw)
In-Reply-To: <20241007064453.2171933-3-steffen.klassert@secunet.com>
On Mon, 7 Oct 2024 08:44:51 +0200 Steffen Klassert wrote:
> Now that we can have percpu xfrm states, the number of active
> states might increase. To get a better lookup performance,
> we cache the used xfrm states at the policy for outbound
> IPsec traffic.
missing kdoc here, FWIW:
include/net/xfrm.h:595: warning: Function parameter or struct member 'state_cache_list' not described in 'xfrm_policy'
next prev parent reply other threads:[~2024-10-07 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 6:44 [PATCH 0/4] xfrm: Add support for RFC 9611 per cpu xfrm states Steffen Klassert
2024-10-07 6:44 ` [PATCH 1/4] xfrm: Add support for per cpu xfrm state handling Steffen Klassert
2024-10-08 16:47 ` Simon Horman
2024-10-11 8:22 ` Steffen Klassert
2024-10-10 18:22 ` kernel test robot
2024-10-07 6:44 ` [PATCH 2/4] xfrm: Cache used outbound xfrm states at the policy Steffen Klassert
2024-10-07 14:26 ` Jakub Kicinski [this message]
2024-10-11 8:21 ` Steffen Klassert
2024-10-07 6:44 ` [PATCH 3/4] xfrm: Add an inbound percpu state cache Steffen Klassert
2024-10-07 6:44 ` [PATCH 4/4] xfrm: Restrict percpu SA attribute to specific netlink message types Steffen Klassert
2024-10-07 6:48 ` [PATCH 0/4] xfrm: Add support for RFC 9611 per cpu xfrm states 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=20241007072623.1b7b24f9@kernel.org \
--to=kuba@kernel.org \
--cc=antony.antony@secunet.com \
--cc=devel@linux-ipsec.org \
--cc=dxu@dxuuu.xyz \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@nohats.ca \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.com \
--cc=tobias@strongswan.org \
/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).