netdev
[Top] [All Lists]

Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxx
Subject: Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5
From: Alex Bligh - linux-kernel <linux-kernel@xxxxxxxxxxx>
Date: Fri, 05 Oct 2001 00:28:44 +0100
Cc: mingo@xxxxxxx, jamal <hadi@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Alexey Kuznetsov <kuznet@xxxxxxxxxxxxx>, Robert Olsson <Robert.Olsson@xxxxxxxxxxx>, Benjamin LaHaise <bcrl@xxxxxxxxxx>, netdev@xxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxxxx>, Simon Kirby <sim@xxxxxxxxxxxxx>, Alex Bligh - linux-kernel <linux-kernel@xxxxxxxxxxx>
In-reply-to: <E15pGhY-0004Qz-00@xxxxxxxxxxxxxxxxx>
References: <E15pGhY-0004Qz-00@xxxxxxxxxxxxxxxxx>
Reply-to: Alex Bligh - linux-kernel <linux-kernel@xxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx


--On Thursday, 04 October, 2001 11:10 PM +0100 Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:

You only think that. After a few minutes the kiddie pulls down your
routing because your route daemons execute no code. Also during the
attack your sshd wont run so you cant log in to find out what is up

There is truth in this. Which is why doing things like
a crude WRED on the card, in the firmware,
(i.e. before it sends the data into user space) is something
we looked at but never got round to.

--
Alex Bligh

<Prev in Thread] Current Thread [Next in Thread>