On Sat, 21 Apr 2007, Ulrich Drepper wrote:
>
> If you do this, and it has been requested many a times, then please
> generalize it. We have the same issue with futexes. If a FUTEX_WAIT
> call is issues the remaining time in the slot should be given to the
> thread currently owning the futex.
And how the hell do you imagine you'd even *know* what thread holds the
futex?
The whole point of the "f" part of the mutex is that it's fast, and we
never see the non-contended case in the kernel.
So we know who *blocks*, but we don't know who actually didn't block.
Linus
-
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]