From: Simon Horman <horms@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org, devel@linux-ipsec.org
Subject: Re: [PATCH RFC ipsec-next] esp: Consolidate esp4 and esp6.
Date: Mon, 27 Oct 2025 15:48:25 +0000 [thread overview]
Message-ID: <aP-USZf42BUtQcgV@horms.kernel.org> (raw)
In-Reply-To: <aPhzm0lzMXGSpf22@secunet.com>
On Wed, Oct 22, 2025 at 08:03:07AM +0200, Steffen Klassert wrote:
> This patch merges common code of esp4.c and esp6.c into
> xfrm_esp.c. This almost halves the size of the ESP
> implementation for the prize of three indirect calls
nit: prize -> price
> on UDP/TCP encapsulation. No functional changes.
>
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
> Tested-by: Tobias Brunner <tobias@strongswan.org>
> ---
> include/net/esp.h | 6 +
> include/net/xfrm.h | 4 +
> net/ipv4/esp4.c | 1067 ++------------------------------------
> net/ipv6/esp6.c | 1093 +++------------------------------------
> net/ipv6/esp6_offload.c | 6 +-
> net/xfrm/Makefile | 1 +
> net/xfrm/xfrm_esp.c | 1025 ++++++++++++++++++++++++++++++++++++
> 7 files changed, 1156 insertions(+), 2046 deletions(-)
Less is more :)
...
> diff --git a/net/ipv6/esp6.c b/net/ipv6/esp6.c
...
> +static int esp6_input_encap(struct sk_buff *skb, struct xfrm_state *x)
> {
> + const struct ipv6hdr *ip6h = ipv6_hdr(skb);
> + int offset = skb_network_offset(skb) + sizeof(*ip6h);
> + int hdr_len = skb_network_header_len(skb);
nit: hrd_len is set here and incremented below,
but otherwise unused in this function.
...
next prev parent reply other threads:[~2025-10-27 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 6:03 [PATCH RFC ipsec-next] esp: Consolidate esp4 and esp6 Steffen Klassert
2025-10-27 15:48 ` Simon Horman [this message]
2025-10-27 16:52 ` Sabrina Dubroca
2025-10-27 17:14 ` [devel-ipsec] " Paul Wouters
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=aP-USZf42BUtQcgV@horms.kernel.org \
--to=horms@kernel.org \
--cc=devel@linux-ipsec.org \
--cc=netdev@vger.kernel.org \
--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).