On Wed, Jul 21, 2004 at 10:52:46AM +0200, Ingo Molnar wrote:
this, if enabled, causes all softirqs to be processed
within ksoftirqd,
and it also breaks out of the softirq loop if preemption of ksoftirqd
has been triggered by a higher-prio task.
You'll still have the latency of finishing the currently executing
softirq, which often includes a loop itself (whose break condition is
based on not hogging the CPU, rather than letting higher priority
tasks in as soon as possible).
-Scott