Andrea Arcangeli wrote:
> >Note: In many cases, spinlock_irqsave doesn't need to do the
> >spinlock_depth thing on UP. [..]
>
> It doesn't need that in SMP either.
An interrupt on another process can wake up a task and set
current->need_resched on this processor.
> >[..] However, not all cases: the code in the
> >lock region might wake up another task.
>
> If you wakeup another task you don't risk to get rescheduled before you
> drop the lock.
Waking up another task may set current->need_resched. But it can't
actually reschedule until reaching the spin_unlock_irqsave. At that
point or some low-latency time later, you need to reschedule to get low
latency.
-- Jamie
-
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/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:27 EST