From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: ebiederm@xmission.com
Subject: [PATCH nf-next 0/4] netfilter: xtables: don't register hooks by default
Date: Thu, 25 Feb 2016 10:08:34 +0100 [thread overview]
Message-ID: <1456391318-11601-1-git-send-email-fw@strlen.de> (raw)
This work changes xtables to register tables only
when the ip(6)tables/arptables command is invoked inside a netns.
Also changes br_netfilter to not add its sabotage hooks until
a bridge is created inside the netns.
The initial namespace isn't affected; hooks are still registered
on module load time there.
netperf receiver running in netns 1.
init ns with empty mangle+filter table.
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
>From ns2 (empty mangle + filter table):
87380 16384 16384 180.00 22034.90
87380 16384 16384 180.00 22355.71
87380 16384 16384 180.00 21906.88
from ns3, no iptables invocations:
87380 16384 16384 180.00 23103.76
87380 16384 16384 180.00 22975.47
87380 16384 16384 180.00 22880.08
-> ~4% delta.
Changes since last iteration:
- dropped the conntrack changes for now
- split patch #2 to make review a bit easier
No other changes.
include/linux/netfilter.h | 29 ++++--------
include/linux/netfilter/x_tables.h | 6 +-
include/linux/netfilter_arp/arp_tables.h | 9 ++-
include/linux/netfilter_ipv4/ip_tables.h | 9 ++-
include/linux/netfilter_ipv6/ip6_tables.h | 9 ++-
net/bridge/br_netfilter_hooks.c | 68 ++++++++++++++++++++++++++++--
net/ipv4/netfilter/arp_tables.c | 66 ++++++++++++++++++-----------
net/ipv4/netfilter/arptable_filter.c | 40 ++++++++++-------
net/ipv4/netfilter/ip_tables.c | 63 ++++++++++++++++-----------
net/ipv4/netfilter/iptable_filter.c | 44 ++++++++++++-------
net/ipv4/netfilter/iptable_mangle.c | 41 ++++++++++++------
net/ipv4/netfilter/iptable_nat.c | 41 +++++++++---------
net/ipv4/netfilter/iptable_raw.c | 38 +++++++++++-----
net/ipv4/netfilter/iptable_security.c | 44 ++++++++++++-------
net/ipv6/netfilter/ip6_tables.c | 65 +++++++++++++++++-----------
net/ipv6/netfilter/ip6table_filter.c | 47 ++++++++++++--------
net/ipv6/netfilter/ip6table_mangle.c | 46 ++++++++++++--------
net/ipv6/netfilter/ip6table_nat.c | 41 +++++++++---------
net/ipv6/netfilter/ip6table_raw.c | 46 ++++++++++++--------
net/ipv6/netfilter/ip6table_security.c | 44 +++++++++++--------
net/netfilter/x_tables.c | 65 +++++++++++++++++-----------
21 files changed, 544 insertions(+), 317 deletions(-)
next reply other threads:[~2016-02-25 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 9:08 Florian Westphal [this message]
2016-02-25 9:08 ` [PATCH nf-next 1/4] netfilter: xtables: prepare for on-demand hook register Florian Westphal
2016-02-25 9:08 ` [PATCH v4 nf-next 2/4] netfilter: xtables: don't hook tables by default Florian Westphal
2016-02-25 9:08 ` [PATCH v4 nf-next 3/4] netfilter: bridge: register hooks only when bridge interface is added Florian Westphal
2016-02-25 9:08 ` [PATCH v4 nf-next 4/4] netfilter: don't call hooks unless needed Florian Westphal
2016-03-02 19:15 ` [PATCH nf-next 0/4] netfilter: xtables: don't register hooks by default Pablo Neira Ayuso
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=1456391318-11601-1-git-send-email-fw@strlen.de \
--to=fw@strlen.de \
--cc=ebiederm@xmission.com \
--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;
as well as URLs for NNTP newsgroup(s).