Pavel Machek wrote:
>> Probably You know better then me how many time schedule() is called in a
>> Linux workstation ( system calls ).
>> Lowering the time the cpu execute schedule() is not as lowering user mode
>> code because schedule() code is mostly interrupt protected.
>> This means a low speed in acknoledging IRQ and hence a worse system response
>> to events.
>schedule() definitely may not be run from interrupt context...
this is passed as OT, but the call to spin_lock_irqsave(runqueue_lock),
I suppose that is going to disable IRQs.
Cheers,
Davide.
-
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/