From: Florian Zwoch <zwoch@backendmedia.com>
To: linux-kernel@vger.kernel.org
Cc: netfilter-devel@lists.netfilter.org, netdev@oss.sgi.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: why does netfilter make upload very slow? (was: Re: e1000 -> 82540EM on linux 2.6.0-test[45] very slow in one direction)
Date: Wed, 15 Oct 2003 10:28:50 +0200 [thread overview]
Message-ID: <3F8D0542.1060101@backendmedia.com> (raw)
In-Reply-To: <20031008153237.GC25743@sunbeam.de.gnumonks.org>
Harald Welte wrote:
>>Would somebody like to explain why netfilter (in kernel, but not in use)
>>makes upload go very slow? I am by no means a network guru, but eager to
>>learn :-)
>
>
> let's get this straight. There are five possible cases
>
> a) CONFIG_NETFILTER disabled. you won't even have the netfilter hooks
> in the network stack (so certainly no netfilter-using modules loaded)
no problem
> b) CONFIG_NETFILTER enabled, but _no_ modules (iptable_filter,
> ip_conntrack, ...) attached to the netfilter hook
no problem
> c) CONFIG_NETFILTER enabled and iptable_filter.o (which pulls ip_tables.o)
> loaded, NO RULES in the table
no problem
> d) CONFIG_NETFILTER enabled and iptable_filter.o (which pulls ip_tables.o)
> loaded, RULES in the table
no problem (as long as i dont load any rules that require ip_conntrack)
> e) CONFIG_NETFILTER enabled and ip_conntrack.o loaded, iptable_filter
> loaded or not, rules or not
*boink*
whenever i try to load ip_conntrack the nic performance drops from 5mb/s
to 200k/s.
still using 2.6.0-test6.
regards,
Florian
next prev parent reply other threads:[~2003-10-15 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 13:13 why does netfilter make upload very slow? (was: Re: e1000 -> 82540EM on linux 2.6.0-test[45] very slow in one direction) ookhoi
2003-10-08 14:54 ` David S. Miller
2003-10-08 15:32 ` Harald Welte
2003-10-15 8:28 ` Florian Zwoch [this message]
2003-10-15 9:48 ` Harald Welte
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=3F8D0542.1060101@backendmedia.com \
--to=zwoch@backendmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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).