From: David Miller <davem@davemloft.net>
To: kadlec@blackhole.kfki.hu
Cc: netdev@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: owner-Match in 2.6.20-rc5 (fwd)
Date: Thu, 25 Jan 2007 13:01:11 -0800 (PST) [thread overview]
Message-ID: <20070125.130111.26966608.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701252121190.26664@blackhole.kfki.hu>
From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Date: Thu, 25 Jan 2007 21:31:56 +0100 (CET)
> The report below was posted on the netfilter user list. Isn't there any
> ill side effect by reverting the change?
Performance regression :-(
This optimization saves a whole handful of heavy atomic operations in
the packet transmit path of TCP.
As I understand it, the owner-Match is not in the upstream tree, and
it's the only thing that cares, so I see no reason to cater for it.
next prev parent reply other threads:[~2007-01-25 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 20:31 owner-Match in 2.6.20-rc5 (fwd) Jozsef Kadlecsik
2007-01-25 20:57 ` Jan Engelhardt
2007-01-25 21:01 ` David Miller [this message]
2007-01-25 21:07 ` Jan Engelhardt
2007-01-25 22:01 ` David Miller
2007-01-25 22:14 ` Jan Engelhardt
2007-01-26 9:05 ` David Miller
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=20070125.130111.26966608.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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).