All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Alexander Sirotkin <demiourgos@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: TCP/UDP checksum in hardware
Date: Fri, 16 Mar 2007 13:35:25 +0100	[thread overview]
Message-ID: <45FA8F0D.9000201@trash.net> (raw)
In-Reply-To: <c4357ccd0703080215p659147bdhefb023d93ae889fd@mail.gmail.com>

Alexander Sirotkin wrote:
> On 3/5/07, Patrick McHardy <kaber@trash.net> wrote:
> 
>> > BTW, while we are on the subject, the overhead of netfilter itself,
>> > i.e. the difference in CPU utilization of kernel with and without
>> > netfilter on the above platform is more than 5%. Is there anybody hear
>> > willing to discuss this ?
>>
>> Is this with netfilter modules (like iptables, conntrack, NAT, ...)
>> loaded or just by enabling netfilter in the configuration?
>>
> Just netfilter, no modules.
> Strangely enough, this only happens with bridge configuration. With
> router configuration the difference in CPU utilization is minor,
> however with bridge it is huge - about 25% on my system.


The bridge-netfilter code includes a number of hooks of its own,
additionally it passes all packets though all IP netfilter hooks
and duplicates quite a bit of the IP layer handling. I'm not very
surprised that its efficiency sucks, although 25% really is a lot.
If you could get profiles we could see if there are possibly some
simple optimizations.

If you don't need IP netfilter on bridged packets you could also
simply disable it through /proc/sys/net/bridge/bridge-nf-call-*.

      reply	other threads:[~2007-03-16 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 15:26 TCP/UDP checksum in hardware Alexander Sirotkin
2007-03-04 17:16 ` Patrick McHardy
2007-03-05  9:49   ` Alexander Sirotkin
2007-03-05 18:06     ` Patrick McHardy
2007-03-08 10:15       ` Alexander Sirotkin
2007-03-16 12:35         ` Patrick McHardy [this message]

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=45FA8F0D.9000201@trash.net \
    --to=kaber@trash.net \
    --cc=demiourgos@gmail.com \
    --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 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.