[lkml]   [2002]   [Sep]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH][RFC] per isr in_progress markers
On Tue, 2002-09-10 at 16:05, David Woodhouse wrote:
> said:
> > 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.
> Note that you can also survive IRQ storms this way -- if all handlers
> returned 'no work was done' and you get over $N irqs per second, disable
> that IRQ for a while.

You can do that without touching any drivers and its better that way

Firstly the "no work was done" check is insufficient if work is being
done but the IRQ rate is too high to keep up.

Secondly the check means mangling all the drivers when you can establish
if work was done anyway by checking bh/userspace has also had some run

I'm all for surviving IRQ storms on a level triggered IRQ, but do it
purely on interrupt rate and measured system progress not on some
assumption that the driver knows what its doing.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.046 / U:0.924 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site