From: Florian Westphal <fw@strlen.de>
To: tingwei liu <tingw.liu@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: NFQUEUE in bridge mode performance poor in the last kernels
Date: Tue, 6 Mar 2012 22:23:37 +0100 [thread overview]
Message-ID: <20120306212337.GA19133@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <CA+qZnSTG+_5y=6dGFqoJwRj0LxMvr2qtmyvykFjfnVgaYgbNPA@mail.gmail.com>
tingwei liu <tingw.liu@gmail.com> wrote:
> In the past few days, I have puzzled by NFQUEUE in bridge mode.
> I have take some test with five kernels.
> 2.6.24.4
> 2.6.36.4
> 2.6.38
> 3.0.8
> 3.1.10
>
> The result is : 2.6.24.4,2.6.26.4,2.6.38 have a goog performance;
> 3.0.8 and 3.1.10 have a poor performance.
> Next is copy from suricata maillist( eric@regit.org )
>
> I'm having a look at it. There has been some changes between the two
> kernel versions (bringing more performances) but it seems there is some
> side effects with bridge.
Might be the 'gro+nfqueue eats MAC header' problem, you could try
commit a8db7b2d197a0d624baab83f0c810b0edbc4ffd0 (netfilter: nf_queue: fix
queueing of bridged gro skbs). Or, disable gro on all bridge ports via
ethtool -K $device gro off
If its not gro related, please provide more information about your
machine, setup, ... etc.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-06 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 2:05 NFQUEUE in bridge mode performance poor in the last kernels tingwei liu
2012-03-06 15:19 ` Eric Dumazet
2012-03-07 0:46 ` tingwei liu
2012-03-07 1:19 ` Eric Dumazet
2012-03-06 21:23 ` Florian Westphal [this message]
2012-03-07 1:26 ` tingwei liu
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=20120306212337.GA19133@Chamillionaire.breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=tingw.liu@gmail.com \
/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).