On 4/21/07, Linus Torvalds <[email protected]> wrote:
And how the hell do you imagine you'd even *know* what thread holds the
futex?
We know this in most cases. This is information recorded, for
instance, in the mutex data structure. You might have missed my "the
interface must be extended" part. This means the PID of the owning
thread will have to be passed done. For PI mutexes this is not
necessary since the kernel already has access to the information.
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.
See above. Believe me, I know how futexes work. But I also know what
additional information we collect. For mutexes and in part for
rwlocks we know which thread owns the sync object. In that case we
can easily provide the kernel with the information.
-
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]
