netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Florian Westphal <fw@strlen.de>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec-next 0/6] xfrm: reduce xfrm_state_afinfo size
Date: Tue, 11 Jun 2019 11:56:53 +0200	[thread overview]
Message-ID: <20190611095653.GG17989@gauss3.secunet.de> (raw)
In-Reply-To: <20190509110748.GU17989@gauss3.secunet.de>

On Thu, May 09, 2019 at 01:07:48PM +0200, Steffen Klassert wrote:
> On Fri, May 03, 2019 at 05:46:13PM +0200, Florian Westphal wrote:
> > xfrm_state_afinfo is a very large struct; its over 4kbyte on 64bit systems.
> > 
> > The size comes from two arrays to store the l4 protocol type pointers
> > (esp, ah, ipcomp and so on).
> > 
> > There are only a handful of those, so just use pointers for protocols
> > that we implement instead of mostly-empty arrays.
> > 
> > This also removes the template init/sort related indirections.
> > Structure size goes down to 120 bytes on x86_64.
> > 
> >  include/net/xfrm.h      |   49 ++---
> >  net/ipv4/ah4.c          |    3 
> >  net/ipv4/esp4.c         |    3 
> >  net/ipv4/esp4_offload.c |    4 
> >  net/ipv4/ipcomp.c       |    3 
> >  net/ipv4/xfrm4_state.c  |   45 -----
> >  net/ipv4/xfrm4_tunnel.c |    3 
> >  net/ipv6/ah6.c          |    4 
> >  net/ipv6/esp6.c         |    3 
> >  net/ipv6/esp6_offload.c |    4 
> >  net/ipv6/ipcomp6.c      |    3 
> >  net/ipv6/mip6.c         |    6 
> >  net/ipv6/xfrm6_state.c  |  137 ----------------
> >  net/xfrm/xfrm_input.c   |   24 +-
> >  net/xfrm/xfrm_policy.c  |    2 
> >  net/xfrm/xfrm_state.c   |  400 +++++++++++++++++++++++++++++++++++-------------
> >  16 files changed, 343 insertions(+), 350 deletions(-)
> > 
> > Florian Westphal (6):
> >       xfrm: remove init_tempsel indirection from xfrm_state_afinfo
> >       xfrm: remove init_temprop indirection from xfrm_state_afinfo
> >       xfrm: remove init_flags indirection from xfrm_state_afinfo
> >       xfrm: remove state and template sort indirections from xfrm_state_afinfo
> >       xfrm: remove eth_proto value from xfrm_state_afinfo
> >       xfrm: remove type and offload_type map from xfrm_state_afinfo
> 
> I have deferred this until after the merge window. I'll
> consider applying them then.

This is now applied to ipsec-next, thanks Florian!

      reply	other threads:[~2019-06-11  9:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 15:46 [PATCH ipsec-next 0/6] xfrm: reduce xfrm_state_afinfo size Florian Westphal
2019-05-03 15:46 ` [PATCH ipsec-next 1/6] xfrm: remove init_tempsel indirection from xfrm_state_afinfo Florian Westphal
2019-05-03 15:46 ` [PATCH ipsec-next 2/6] xfrm: remove init_temprop " Florian Westphal
2019-05-03 15:46 ` [PATCH ipsec-next 3/6] xfrm: remove init_flags " Florian Westphal
2019-05-03 15:46 ` [PATCH ipsec-next 4/6] xfrm: remove state and template sort indirections " Florian Westphal
2019-05-03 15:46 ` [PATCH ipsec-next 5/6] xfrm: remove eth_proto value " Florian Westphal
2019-05-03 15:46 ` [PATCH ipsec-next 6/6] xfrm: remove type and offload_type map " Florian Westphal
2019-05-09 11:07 ` [PATCH ipsec-next 0/6] xfrm: reduce xfrm_state_afinfo size Steffen Klassert
2019-06-11  9:56   ` 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=20190611095653.GG17989@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --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).