From: Rusty Russell <rusty@rustcorp.com.au>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 networking/routing slowdown
Date: Sat, 28 Jul 2001 17:10:48 +1000 [thread overview]
Message-ID: <E15QOFN-0007NI-00@localhost> (raw)
In-Reply-To: Your message of "Thu, 26 Jul 2001 14:25:31 +0200." <20010726142531.G1024@informatics.muni.cz>
In message <20010726142531.G1024@informatics.muni.cz> you write:
> seconds to echo a single keystroke). I've figured out that ipchains.o in 2.4
> is linked with connection tracking, which probably causes the main slowdown.
Yes, you're paying for full connection tracking with the compatibility
stuff. If you just want filtering, switch to iptables (should be
pretty easy for you).
> After rmmod ipchains the server seems to have its interactive performace
> back on normal speed, but routing performance still sucks: FTP between
> two hosts on different interfaces gets about 1600 KBytes/s (in 2.2 kernel
> it runs at 9900 KBytes/s). When I disable CONFIG_NET_HW_FLOWCONTROL,
> the throughput increases (ugh!) to 2300 KBytes/s.
Hmmm... this I don't know.
Rusty.
--
Premature optmztion is rt of all evl. --DK
prev parent reply other threads:[~2001-07-29 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 12:25 Linux 2.4 networking/routing slowdown Jan Kasprzak
2001-07-28 7:10 ` Rusty Russell [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=E15QOFN-0007NI-00@localhost \
--to=rusty@rustcorp.com.au \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@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