Messages in this thread |  | | Date | Fri, 05 Oct 2001 00:25:41 +0100 | From | Alex Bligh - linux-kernel <> | Subject | Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5 |
| |
--On Thursday, 04 October, 2001 3:01 PM -0700 Simon Kirby <sim@netnation.com> wrote:
> Ingo is not limiting interrupts to make it drop packets and forget things > just so that userspace can proceed. Instead, he is postponing servicing > of the interrupts so that the card can batch up more packets and the > interrupt will retrieve more at once rather than continually leaving and > entering the interrupt to just pick up a few packets. Without this, the > interrupt will starve everything else, and nothing will get done.
Ah OK. in this case already looking at interupt coalescing at firmware level which mitigates this 'earlier on', however even this stratgy fails at higher pps levels => i.e. in these circumstances the card buffer is already full-ish, as the interrupt has already been postponed, and postponing it further can only cause dropped packets through buffer overrun.
-- Alex Bligh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |