From: Michael Knigge <Michael.Knigge@set-software.de>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG REPORT: Massive performance drop in routing throughput with 2.4.21
Date: Mon, 23 Jun 2003 07:14:09 GMT [thread overview]
Message-ID: <20030623.7140952@knigge.local.net> (raw)
In-Reply-To: <20030616143451.26d3de7e.skraw@ithnet.com>
Hi all,
could please someone tell me if this issue is fixed in –ac2 or .22pre
?
Thank you,
Michael
next prev parent reply other threads:[~2003-06-23 7:01 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 [this message]
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 ` BUG: Massive performance drop in routing throughput " Stephan von Krawczynski
2003-06-18 14:16 ` 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=20030623.7140952@knigge.local.net \
--to=michael.knigge@set-software.de \
--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