SA_INTERRUPT

From: Sandy Harris (sandy@storm.ca)
Date: Sat Sep 30 2000 - 21:50:21 EDT

Next message: Chris Faylor: "Re: What is up with Redhat 7.0?"

Previous message: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Chris Faylor: "Re: What is up with Redhat 7.0?"
Previous message: Matthew Wilcox: "Re: [RFC] Imminent death of /proc/locks predicted; film at 11"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:52:26 EDT