| To: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5 |
| From: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
| Date: | Mon, 8 Oct 2001 10:03:57 -0500 (CDT) |
| Cc: | Andrea Arcangeli <andrea@xxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, jamal <hadi@xxxxxxxxxx>, Linux-Kernel <linux-kernel@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxxxx> |
| In-reply-to: | <E15qbtV-0000hd-00@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Mon, 8 Oct 2001, Alan Cox wrote:
> > Of course we agree that such a "polling router/firewall" behaviour must
> > not be the default but it must be enabled on demand by the admin via
> > sysctl or whatever else userspace API. And I don't see any problem with
> > that.
>
> No I don't agree. "Stop random end users crashing my machine at will" is not
> a magic sysctl option - its a default.
I think (Ingo's?) analogy of an airbag was appropriate, if that's indeed
how the code winds up functioning.
Having a mechanism that prevents what would otherwise be a lockup is
useful. NAPI is useful. Having both would be nice :)
Jeff
|
| Previous by Date: | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5, Alan Cox |
|---|---|
| Next by Date: | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5, Alan Cox |
| Previous by Thread: | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5, Alan Cox |
| Next by Thread: | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5, Alan Cox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |