Don Becker has some text at:
http://www.scyld.com/expert/irq-conflict.html
which includes a section:
> Why SA_INTERRUPT in the SCSI drivers is a Bad Thing
> ... it could potentially have a very negative impact on all other interrupt-driven
> kernel service. That includes just about everything ...
>
> I believe that very few complex devices can be correctly run by a device driver
> that uses SA_INTERRUPT.
So I grepped drivers/*/*.c in the nearest handy kernel source, which happened to be
2.2.16, and found 113 uses of SA_INTEERUPT, 64 in drivers/scsi/*.c and the rest spread
around.
Do we have a problem? Should it be fixed as part of the cleanup before 2.4.0?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
