> What it will _not_ do is to preempt a process already running on that
> other CPU. From reschedule_idle():
>
> * [We can try to preempt low-priority processes on other CPUs in
> * 2.3. Also we can try to use the avg_slice value to predict
> * 'likely reschedule' events even on other CPUs.]
>
> Ingo, any thoughts? Seems that if for any reason all wakeup interrupts
> arrive at the same CPU which is running the SCHED_FIFO task, then we
> will _never_ perform any successful wakeups without first exhausting the
> other CPU's current timeslice.
yes i have a patch for this but it's not straightforward enough for 2.2.
(ie. a 50k patch) It has to do things like a full goodness() run for every
CPU in wakeup(), which is less than ideal.
-- mingo
-
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/