All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br, alan@lxorguk.ukuu.org.uk
Subject: Re: BUG REPORT: Massive performance drop in routing throughput with 2.4.21
Date: Mon, 16 Jun 2003 14:34:51 +0200	[thread overview]
Message-ID: <20030616143451.26d3de7e.skraw@ithnet.com> (raw)
In-Reply-To: <20030616141806.6a92f839.skraw@ithnet.com>

Additional information:

I found another setup which has the same problem reproducable. Since this is no
production unit I can test patches. It may be important to the problem that
there are _three_ network cards, as the test-setup shows no degression in
simple 1-1 through routing but using a third network card ot the same box makes
it woe.

Hope this helps.
Stephan

  reply	other threads:[~2003-06-16 12:21 UTC|newest]

Thread overview: 16+ 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 [this message]
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             ` BUG: Massive performance drop in routing throughput " Stephan von Krawczynski
2003-06-18 14:16               ` Chris Friesen
2003-06-18 14:36                 ` BUG: Massive performance drop in routing throughput with 2.4.21 Mr. James W. Laferriere
2003-06-18 14:56                   ` Chris Friesen
2003-06-18 17:20               ` BUG: Massive performance drop in routing throughput with 2.4.21 (62KB) 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=20030616143451.26d3de7e.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.