lkml.org 
[lkml]   [2004]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Why no interrupt priorities?
Grover, Andrew wrote:
>
> Is the assumption that hardirq handlers are superfast also the reason
> why Linux calls all handlers on a shared interrupt, even if the first
> handler reports it was for its device?
>
No, it is the other way around. hardirq handlers have to be superfast
because linux usually _have to_ call all the handlers of a shared irq.

The fact that one device did indeed have an interrupt for us doesn't mean
that the others didn't. So all of them have to be checked to be safe.

If this becomes a performance problem, make sure that no _busy_ irqs
are shared. The easy way is to shuffle pci cards around, or set
jumpers/switches or software controlled options. Or resort to
reprogramming the APIC in extreme cases.

Helge Hafting

-
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/

\
 
 \ /
  Last update: 2005-03-22 14:01    [W:0.082 / U:9.624 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site