From: Lukas Wunner <lukas@wunner.de>
To: "Pablo Neira Ayuso" <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Eric Dumazet <edumazet@google.com>, Thomas Graf <tgraf@suug.ch>,
Laura Garcia Liebana <nevola@gmail.com>,
John Fastabend <john.fastabend@gmail.com>
Subject: [PATCH nf-next v4 0/5] Netfilter egress hook
Date: Fri, 22 Jan 2021 09:47:00 +0100 [thread overview]
Message-ID: <cover.1611304190.git.lukas@wunner.de> (raw)
Netfilter egress hook, 4th iteration:
Previously traffic control suffered a performance degradation with this
series applied. Not anymore, see patch [1/5].
Pablo added netfilter egress handling to af_packet, patch [5/5].
Pablo also moved the netfilter egress hook behind traffic control to
address an objection from Daniel Borkmann, see patch [4/5]. The commit
message was amended with Laura's and Pablo's use cases to make it clear
that the series is no longer motivated by an out-of-tree module.
A bunch of small performance improvements and bugfixes were applied.
Please review and test. Thanks!
Link to previous version:
https://lore.kernel.org/netfilter-devel/cover.1598517739.git.lukas@wunner.de/
Lukas Wunner (4):
net: sched: Micro-optimize egress handling
netfilter: Rename ingress hook include file
netfilter: Generalize ingress hook include file
netfilter: Introduce egress hook
Pablo Neira Ayuso (1):
af_packet: Introduce egress hook
include/linux/netdevice.h | 4 ++
include/linux/netfilter_ingress.h | 58 ----------------
include/linux/netfilter_netdev.h | 112 ++++++++++++++++++++++++++++++
include/uapi/linux/netfilter.h | 1 +
net/core/dev.c | 16 +++--
net/netfilter/Kconfig | 8 +++
net/netfilter/core.c | 34 ++++++++-
net/netfilter/nft_chain_filter.c | 4 +-
net/packet/af_packet.c | 35 ++++++++++
9 files changed, 206 insertions(+), 66 deletions(-)
delete mode 100644 include/linux/netfilter_ingress.h
create mode 100644 include/linux/netfilter_netdev.h
--
2.29.2
next reply other threads:[~2021-01-22 8:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:47 Lukas Wunner [this message]
2021-01-22 8:47 ` [PATCH nf-next v4 1/5] net: sched: Micro-optimize egress handling Lukas Wunner
2021-01-22 9:40 ` Eric Dumazet
2021-01-24 10:33 ` Lukas Wunner
2021-01-25 19:39 ` Jakub Kicinski
2021-01-26 8:58 ` Dan Carpenter
2021-01-30 16:00 ` Lukas Wunner
2021-01-24 3:26 ` Jakub Kicinski
2021-01-24 10:46 ` Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 2/5] netfilter: Rename ingress hook include file Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 3/5] netfilter: Generalize " Lukas Wunner
2021-01-22 8:47 ` [PATCH nf-next v4 4/5] netfilter: Introduce egress hook Lukas Wunner
2021-01-26 19:13 ` Daniel Borkmann
2021-09-11 21:26 ` Lukas Wunner
2021-09-15 9:45 ` Daniel Borkmann
2021-01-22 8:47 ` [PATCH nf-next v4 5/5] af_packet: " Lukas Wunner
2021-01-22 16:13 ` Willem de Bruijn
2021-01-24 11:14 ` Lukas Wunner
2021-01-24 16:18 ` Willem de Bruijn
2021-01-30 16:26 ` Lukas Wunner
2021-01-30 16:58 ` Willem de Bruijn
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=cover.1611304190.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=ast@kernel.org \
--cc=coreteam@netfilter.org \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=john.fastabend@gmail.com \
--cc=kadlec@netfilter.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nevola@gmail.com \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.