From: Stephan von Krawczynski <skraw@ithnet.com>
To: "David S. Miller" <davem@redhat.com>
Cc: babydr@baby-dragons.com, linux-kernel@vger.kernel.org
Subject: Re: BUG: Massive performance drop in routing throughput with 2.4.21 (62KB)
Date: Wed, 18 Jun 2003 15:10:34 +0200 [thread overview]
Message-ID: <20030618151034.0a84b2e2.skraw@ithnet.com> (raw)
In-Reply-To: <1055880260.19796.7.camel@rth.ninka.net>
On 17 Jun 2003 13:04:20 -0700
"David S. Miller" <davem@redhat.com> wrote:
> On Tue, 2003-06-17 at 12:33, Mr. James W. Laferriere wrote:
> > Hello All , Here goes . I made 'me too'ism in another thread
> > that may be related to what I am presenting here . After my .sig
> > is what I hope to be enough pertitanent information to get the bug
> > stomped on . This is driving me crazy . Also if someone would
> > like to point me at a URL:/Method(s)/... to be able to acquire
> > further information that would make the effort for those that
> > really can code in the kernel jobs easier please do .
> > The slow down mentioned below happens with any network based
> > connection . JimL
>
> You can start by reporting the bug and all your debugging
> informtion to the correct list.
>
> Networking developers DO NOT sit on linux-kernel, it's too high
> volume for them. So use the correct list to report such
> problems.
Maybe I should have made it a bit clearer in my original post to this thread:
the thing is a show-stopper. You can watch a 2.4.21 box drop down its
throughput to somewhere around 2-4 kByte/sec on a 100 MBit/sec switched
network. You have to setup a real routing-environment testbed to notice the
problem. I did not see it using any of the rc's as a simple host with all kinds
of network applications (including high volume nfs), but not routing...
Regards,
Stephan
next prev parent reply other threads:[~2003-06-18 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 12:18 BUG REPORT: Massive performance drop in routing throughput with 2.4.21 Stephan von Krawczynski
2003-06-16 12:34 ` Stephan von Krawczynski
2003-06-23 7:14 ` Michael Knigge
2003-06-23 11:42 ` Alan Cox
2003-06-16 12:47 ` Maciej Soltysiak
2003-06-16 12:51 ` Stephan von Krawczynski
2003-06-16 13:10 ` Martin Zwickel
2003-06-16 18:18 ` Mr. James W. Laferriere
2003-06-17 19:33 ` BUG: Massive performance drop in conncetion time with 2.4.21 (62KB) Mr. James W. Laferriere
2003-06-17 20:04 ` David S. Miller
2003-06-18 13:10 ` Stephan von Krawczynski [this message]
2003-06-18 14:16 ` BUG: Massive performance drop in routing throughput " Chris Friesen
2003-06-18 17:20 ` David S. Miller
2003-06-19 12:24 ` Stephan von Krawczynski
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=20030618151034.0a84b2e2.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=babydr@baby-dragons.com \
--cc=davem@redhat.com \
--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