On Mon, 3 Jul 2000, Richard Gooch wrote:
> Let me point out a couple of examples which show just how difficult
> this "fast scheduling" business is, and why we should leave these
> things to RTLinux instead:
>
> - some (broken) motherboard/IDE chipsets will lock up hard if you take
> another interrupt while servicing the IDE interrupt. Hence, the
> default IDE driver does/did disable IRQs in its interrupt
> handler. This doesn't just foul up process latencies, it can kill
You then walk away form onboard host and use the three offboards that can
now parse interrupts. The chipsets allow quick test and get out if it is
not our interrupt.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:16 EST