From: Lutz Vieweg <lkv@isg.de>
To: kas@informatics.muni.cz, linux-kernel@vger.kernel.org
Cc: unix@fi.muni.cz
Subject: Re: [Fwd: Linux 2.4 networking/routing slowdown]
Date: Thu, 26 Jul 2001 14:45:32 +0200 [thread overview]
Message-ID: <3B6010EC.B7428A0D@isg.de> (raw)
In-Reply-To: <3B600EAD.3F8F9A70@isg.de>
Jan Kasprzak <kas@informatics.muni.cz> wrote:
> > I have tried to upgrade my firewall to 2.4 kernel (2.4.7), and I have
> > observed a major slowdown of the network speed.
We observed a similar problem, hunted it down via kernel profiling:
When we used ipchains to establish a port redirection (just one
rule, map one port to another), the network would become rediculously
slow after some time of use, causing the CPU to spend almost 100%
as "system time".
We found that the expensive kernel functions were redir_cmp and unredir_cmp,
which were called an unreasonable amount of times by find_redir - seems the
iteration over the list there is quite lengthy...
We didn't investigate the problem further, but found that by using
"iptables" instead of the obsolete "ipchains" to establish the redirection
rule, everything was fine again.
So my advice would be to try iptables and see if your problem goes away
as well.
Regards,
Lutz Vieweg
--
Dipl. Phys. Lutz Vieweg | email: lkv@isg.de
Innovative Software AG | Phone/Fax: +49-69-505030 -120/-505
Feuerbachstrasse 26-32 | http://www.isg.de/people/lkv/
60325 Frankfurt am Main | ^^^ PGP key available here ^^^
next parent reply other threads:[~2001-07-26 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B600EAD.3F8F9A70@isg.de>
2001-07-26 12:45 ` Lutz Vieweg [this message]
2001-07-26 12:54 ` [Fwd: Linux 2.4 networking/routing slowdown] Jan Kasprzak
[not found] ` <20010726152322.A1339@codefountain.com>
2001-07-26 13:33 ` Jan Kasprzak
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=3B6010EC.B7428A0D@isg.de \
--to=lkv@isg.de \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=unix@fi.muni.cz \
/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