netdev
[Top] [All Lists]

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

To: hadi@xxxxxxxxxx (jamal)
Subject: Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 8 Oct 2001 16:22:16 +0100 (BST)
Cc: alan@xxxxxxxxxxxxxxxxxxx (Alan Cox), jgarzik@xxxxxxxxxxxxxxxx (Jeff Garzik), andrea@xxxxxxx (Andrea Arcangeli), mingo@xxxxxxx (Ingo Molnar), linux-kernel@xxxxxxxxxxxxxxx (Linux-Kernel), netdev@xxxxxxxxxxx, torvalds@xxxxxxxxxxxxx (Linus Torvalds)
In-reply-to: <Pine.GSO.4.30.0110081106500.5473-100000@xxxxxxxxxxxxxxxx> from "jamal" at Oct 08, 2001 11:09:57 AM
Sender: owner-netdev@xxxxxxxxxxx
> On Mon, 8 Oct 2001, Alan Cox wrote:
> 
> > NAPI is important - the irq disable tactic is a last resort. If the right
> > hardware is irq flood aware it should only ever trigger to save us from
> > irq routing errors (eg cardbus hangs)
> 
> Agreed. As long as the IRQ flood protector can do proper isolation.
> Here's hat i see on my dell latitude laptop with a built in ethernet (not
> cardbus related ;->)

It doesnt save you from horrible performance. NAPI is there to do that, it
saves you from a dead box. You can at least rmmod the cardbus controller
with protection in place (or go looking for the problem with a debugger)

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