| To: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5 |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Mon, 8 Oct 2001 11:09:57 -0400 (EDT) |
| Cc: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>, Andrea Arcangeli <andrea@xxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Linux-Kernel <linux-kernel@xxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxx> |
| In-reply-to: | <E15qc5N-0000p5-00@xxxxxxxxxxxxxxxxx> |
| 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 ;->)
-------------------------------
[root@jzny /root]# cat /proc/interrupts
CPU0
0: 29408219 XT-PIC timer
1: 332192 XT-PIC keyboard
2: 0 XT-PIC cascade
10: 643040 XT-PIC Texas Instruments PCI1410 PC card Cardbus
Controller, eth0
11: 17 XT-PIC usb-uhci
12: 2207062 XT-PIC PS/2 Mouse
14: 307504 XT-PIC ide0
NMI: 0
LOC: 0
ERR: 0
MIS: 0
-----------------------------
cheers,
jamal
|
| 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] |