netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 ipsec-next 00/11] xfrm: remove xfrm_mode indirections
Date: Wed, 3 Apr 2019 10:31:35 +0200	[thread overview]
Message-ID: <20190403083135.GA12873@bistromath.localdomain> (raw)
In-Reply-To: <20190329201632.11149-1-fw@strlen.de>

2019-03-29, 21:16:21 +0100, Florian Westphal wrote:
> This series removes all function pointers from the xfrm_mode struct.
> They are either replaced by direct calls or a static helper.
> 
> This reduces code size: even merging all xfrm{4,6}_,mode* modules
> into the core reduces total size, as the infrastructure to maintain
> dynamic (un)register can be removed.
> 
> There are more opportunities for indirection avoidance, e.g. in
> xfrm_type.  I plan to follow up once/if this series is accepted.
> 
> Tested with xfrm tunnel mode via netns with esp/aead.
> 
> I'd like thank Benedict Wong for running Android unit tests
> and taking the time to bisect a tunnel mode breakage added by
> v1 of this patch set.
> 
> I've addressed the comments/feedback from Sabrina and Eyal.
> The kbuild robot reported build breakage in patch #8 is fixed
> as well.
> 
> I've not addressed the sparse warning reported by the
> kbuild robot -- those warnings are in code not touched
> by this patch set.
> 
> Florian Westphal (11):
>       xfrm: place af number into xfrm_mode struct
>       xfrm: prefer family stored in xfrm_mode struct
>       xfrm: remove input indirection from xfrm_mode
>       xfrm: remove output indirection from xfrm_mode
>       xfrm: remove xmit indirection from xfrm_mode
>       xfrm: remove gso_segment indirection from xfrm_mode
>       xfrm: remove input2 indirection from xfrm_mode
>       xfrm: remove output2 indirection from xfrm_mode
>       xfrm: remove afinfo pointer from xfrm_mode
>       xfrm: make xfrm modes builtin
>       xfrm: store xfrm_mode directly, not its address

Series:
Reviewed-by: Sabrina Dubroca <sd@queasysnail.net>

-- 
Sabrina

  parent reply	other threads:[~2019-04-03  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 20:16 [PATCH v2 ipsec-next 00/11] xfrm: remove xfrm_mode indirections Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 01/11] xfrm: place af number into xfrm_mode struct Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 02/11] xfrm: prefer family stored in " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 03/11] xfrm: remove input indirection from xfrm_mode Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 04/11] xfrm: remove output " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 05/11] xfrm: remove xmit " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 06/11] xfrm: remove gso_segment " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 07/11] xfrm: remove input2 " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 08/11] xfrm: remove output2 " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 09/11] xfrm: remove afinfo pointer " Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 10/11] xfrm: make xfrm modes builtin Florian Westphal
2019-03-29 20:16 ` [PATCH v2 ipsec-next 11/11] xfrm: store xfrm_mode directly, not its address Florian Westphal
2019-04-03  8:31 ` Sabrina Dubroca [this message]
2019-04-10 11:17 ` [PATCH v2 ipsec-next 00/11] xfrm: remove xfrm_mode indirections 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=20190403083135.GA12873@bistromath.localdomain \
    --to=sd@queasysnail.net \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.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).