From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: David Miller <davem@davemloft.net>,
"acme@ghostprotocols.net" <acme@ghostprotocols.net>,
"jesse.brandeburg@gmail.com" <jesse.brandeburg@gmail.com>,
"fedora-kernel-list@redhat.com" <fedora-kernel-list@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: fedora 14 kernel performance with ip forwarding workload
Date: Wed, 06 Apr 2011 23:11:09 +0200 [thread overview]
Message-ID: <1302124269.2701.36.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.WNT.2.00.1104061400320.6556@JBRANDEB-DESK2.amr.corp.intel.com>
Le mercredi 06 avril 2011 à 14:08 -0700, Brandeburg, Jesse a écrit :
> Thanks for the replies,
> Yes indeed, I bet that conntrack was the item that caused the grief I saw.
> In fact turning off CONFIG_NETFILTER disables conntrack and solved my
> problem. :-)
>
> Now the question is how to get the netfiltery/conntracky goodness without
> impacting those who want to go fast, maybe without a helmet.
Thats pretty simple, just load netfilter modules if necessary.
If not loaded, cost is pretty small, being predicted branches.
prev parent reply other threads:[~2011-04-06 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 18:51 fedora 14 kernel performance with ip forwarding workload Jesse Brandeburg
2011-04-06 19:12 ` David Miller
2011-04-06 19:57 ` Arnaldo Carvalho de Melo
2011-04-06 20:02 ` David Miller
[not found] ` <20110406.130239.232756965.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-04-06 20:13 ` Arnaldo Carvalho de Melo
2011-04-06 20:18 ` Eric Dumazet
2011-04-06 20:29 ` David Miller
2011-04-06 20:32 ` Eric Dumazet
2011-04-06 21:08 ` Brandeburg, Jesse
2011-04-06 21:11 ` Eric Dumazet [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=1302124269.2701.36.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=davem@davemloft.net \
--cc=fedora-kernel-list@redhat.com \
--cc=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.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