From: David Woodhouse <dwmw2@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: fw@strlen.de, pablo@netfilter.org, rga@amazon.de,
bridge@lists.linux-foundation.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
aliguori@amazon.com, nbd@openwrt.org
Subject: Re: [RFC PATCH v2] bridge: make it possible for packets to traverse the bridge without hitting netfilter
Date: Fri, 09 Mar 2018 16:15:14 +0000 [thread overview]
Message-ID: <1520612114.29061.15.camel@infradead.org> (raw)
In-Reply-To: <20180309.105724.519703919967625754.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Fri, 2018-03-09 at 10:57 -0500, David Miller wrote:
> From: David Woodhouse <dwmw2@infradead.org>
> Date: Fri, 09 Mar 2018 15:31:15 +0000
>
> > Eschewing a 15% speedup on the basis that "well, even though we've had
> > three of these already for a decade, we're worried that adding a fourth
> > might open the floodgates to further patches" does seem a little odd to
> > me, FWIW.
>
> The cost we are dealing with is a fundamental one which is a result of
> the hook design.
>
> Indirect calls are killer.
>
> Indirect calls are even more killer now in the age of Spectre and
> retpolines.
Imre's 15% measurement was, obviously, before that. We should redo it
and confirm the numbers.
> I definitely would rather see the fundamental issue addressed rather
> than poking at it randomly with knobs for this case and that.
Yeah. What do you think of the suggestion I made — that a given hook
should automatically disable itself if it tautologically does nothing?
Coupled with notifiers for when the rules change, to re-enable the
hooks again? I confess I don't even know how realistic that is.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-03-09 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:26 [RFC PATCH v2] bridge: make it possible for packets to traverse the bridge without hitting netfilter Imre Palik
2015-02-23 16:06 ` Florian Westphal
2015-02-26 10:19 ` Imre Palik
2015-02-26 16:34 ` David Miller
2015-03-06 10:34 ` Imre Palik
2015-03-06 14:29 ` Pablo Neira Ayuso
2015-03-06 16:37 ` Florian Westphal
2018-03-09 15:31 ` David Woodhouse
2018-03-09 15:57 ` David Miller
2018-03-09 16:15 ` David Woodhouse [this message]
2018-03-09 16:26 ` Florian Westphal
2015-03-06 17:49 ` David Miller
2015-02-26 21:17 ` Felix Fietkau
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=1520612114.29061.15.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=aliguori@amazon.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rga@amazon.de \
--cc=stephen@networkplumber.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).