> What you really care about is limiting the total amount of CPU time
> used for interrupt processing so that usermode progress is made.
> [...]
exactly. The estimator in -D9 tries to achieve precisely this, both
hardirqs and softirqs are measured.
> Silencing a specific target cannot be done by IRQ masking, you have to
> ask the controller to shut up. It may be the default "shut up" handler
> is disable_irq but that is non optimal.
this could be done later on, but i think this is out of question for 2.4,
as it needs extensive changes in irq handler and network driver API.
Ingo
-
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/