* Steven Rostedt <[email protected]> wrote:
> On an SMP machine, there may even be a chance of a lower priority
> process that gets it. That would be possible if the low priority
> process on the other CPU tries to grab the lock just after it was
> released but before the just woken up high priorty processes get
> scheduled. So there's a window where the lock is open, and the lower
> priority process snagged it just before the others got in.
that's always a possibility, on UP too: if a lower priority task manages
to acquire a lock 'just before' a highprio thread got interested in it
there's no way to undo that.
but for the other reasons the explicit approach looks better.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
