Linux Netfilter development
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nf-next 0/4] netfilter: nf_tables: shrink stack usage a bit more
Date: Fri, 14 Apr 2023 15:01:30 +0200	[thread overview]
Message-ID: <20230414130134.29040-1-fw@strlen.de> (raw)

Get rid of a few redundant pointers in the traceinfo structure.
The three removed pointers are used in the expression evaluation loop,
so gcc keeps them in registers.  Passing them to the (inlined) helpers
thus doesn't increase nft_do_chain text size, while stack is reduced
by another 24 bytes on 64bit arches.

These patches apply on top of 'netfilter: nf_tables: shrink jump stack size'.

Florian Westphal (4):
  netfilter: nf_tables: remove unneeded conditional
  netfilter: nf_tables: do not store pktinfo in traceinfo structure
  netfilter: nf_tables: do not store verdict in traceinfo structure
  netfilter: nf_tables: do not store rule in traceinfo structure

 include/net/netfilter/nf_tables.h | 12 +++------
 net/netfilter/nf_tables_core.c    | 42 ++++++++++++++++---------------
 net/netfilter/nf_tables_trace.c   | 38 +++++++++++++++-------------
 3 files changed, 46 insertions(+), 46 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-04-14 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 13:01 Florian Westphal [this message]
2023-04-14 13:01 ` [PATCH nf-next 1/4] netfilter: nf_tables: remove unneeded conditional Florian Westphal
2023-04-14 13:01 ` [PATCH nf-next 2/4] netfilter: nf_tables: do not store pktinfo in traceinfo structure Florian Westphal
2023-04-14 13:01 ` [PATCH nf-next 3/4] netfilter: nf_tables: do not store verdict " Florian Westphal
2023-04-14 13:01 ` [PATCH nf-next 4/4] netfilter: nf_tables: do not store rule " Florian Westphal

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=20230414130134.29040-1-fw@strlen.de \
    --to=fw@strlen.de \
    --cc=netfilter-devel@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