Messages in this thread | | | Date | Mon, 09 Sep 2002 13:08:34 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH][RFC] per isr in_progress markers |
| |
Ingo Molnar wrote: > > On Mon, 9 Sep 2002, Zwane Mwaikambo wrote: > > > As an aside, i just had an idea for another way to improve interrupt > > handling latency. Instead of walking through all the isrs in the chain, > > we can have an isr flag wether it was the source of the irq, and if so > > we stop right there and not walk through the other isrs. Obviously > > taking into account that some devices are dumb and have no real way of > > determining. > > this is something i have a 0.5 MB patch for that touches a few hundred > drivers. I can dust it off if there's demand - it will break almost > nothing because i've done the hard work of adding the default 'no work was > done' bit to every driver's IRQ handler. >
Does that code re-order the chain dynamically?
(My laptop shares an interrupt between the cardbus controller and the cardbus ethernet controller. The ethernet controller generates 1000 interrupts per second. The cardbus controller generates 2 interrupts per day. yenta_interrupt is really, really slow). - 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/
| |