Skip to contentSkip to conversation

Why no interrupt priorities?

DISCUSSION Albert Cahalan 1 participant 1 message Feb 27, 2004

lore
Share & tools
lore
#0 lore raw
Quoted 11 lines · Tim Bird

What's the rationale for not supporting interrupt priorities in the kernel?

We're having a discussion of this in one of our CELF working groups, and it would help if someone could explain why an interrupt priority system has never been adopted in the mainstream Linux kernel. (I know that some implementations have been written and proposed).

Is there a strong policy against such a thing, or is it just that the right implementation has not come along?

Simple reason: shared interrupts

Besides that, what you'd really want is a mask, not a level. You might like to block out all network interrupts while still allowing SCSI interrupts. At some other time, you'd like the opposite. None of the common hardware (PC, Mac, etc.) is at all friendly to using a mask, even if you don't have shared interrupts.

So the policy is: get in, shut the hardware up, set a flag or wake something up, and get out. Interrupt handlers are supposed to be very fast and simple. Put the real work elsewhere.