From: Jonathan Morton <chromi@cyberspace.org>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to optimize routing performance
Date: Thu, 15 Mar 2001 19:30:56 +0000 [thread overview]
Message-ID: <l0313030eb6d6c75fcbf8@[192.168.239.101]> (raw)
In-Reply-To: <15025.3553.176799.382488@robur.slu.se>
In-Reply-To: <Pine.LNX.4.33.0103152137240.1320-100000@duckman.distro.conectiva> <15024.53099.41814.716733@robur.slu.se> <Pine.LNX.4.33.0103152137240.1320-100000@duckman.distro.conectiva>
> And we have done experiments with controlling interrupts and running
> the RX at "lower" priority. The idea is take RX-interrupt and immediately
> postponing the RX process to tasklet. The tasklet opens for new RX-ints.
> when its done. This way dropping now occurs outside the box since and
> dropping becomes very undramatically.
<snip>
> A bit of explanation. Above is output from tulip driver. We are forwarding
> 44079 and we are dropping 49913 packets per second! This box has
> full BGP. The DoS attack was going on for about 30 minutes BGP survived
> and the box was manageable. Under a heavy attack it still performs well.
Nice. Any chance of similar functionality finding its' way outside the
Tulip driver, eg. to 3c509 or via-rhine? I'd find those useful, since one
or two of my Macs appear to be capable of generating pseudo-DoS levels of
traffic under certain circumstances which totally lock a 486 (for the
duration) and heavily load a P166 - even though said Macs "only" have
10baseT Ethernet.
OTOH, proper management of the circumstances under which this flooding
occurs (it's an interaction bug which occurs when the Linux machine ends up
with a zero-sized TCP receive window) would also be rather helpful.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
next prev parent reply other threads:[~2001-03-15 19:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 0:38 Rik van Riel
2001-03-15 14:19 ` Robert Olsson
2001-03-15 18:45 ` Robert Olsson
2001-03-15 19:30 ` Jonathan Morton [this message]
2001-03-15 19:54 ` Robert Olsson
2001-03-15 21:01 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2001-03-16 7:21 Mårten Wikström
2001-03-16 8:08 ` Martin Josefsson
[not found] <3AB12640.79E7B4FB@colorfullife.com>
2001-03-15 21:39 ` Robert Olsson
2001-03-15 20:16 Jonathan Earle
2001-03-15 7:23 Mårten Wikström
2001-03-15 12:32 ` Rik van Riel
2001-03-15 16:20 ` Martin Josefsson
2001-03-15 18:09 ` J Sloan
2001-03-16 2:05 ` Rik van Riel
2001-03-15 19:17 ` J Sloan
2001-03-15 19:36 ` Gregory Maxwell
2001-03-15 19:45 ` J Sloan
2001-03-15 19:44 ` Mike Kravetz
2001-03-16 2:35 ` Rik van Riel
2001-03-15 19:28 ` J Sloan
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='l0313030eb6d6c75fcbf8@[192.168.239.101]' \
--to=chromi@cyberspace.org \
--cc=Robert.Olsson@data.slu.se \
--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
all inboxes | Powered by JetHome®