Re: first little problem with private futexes

Ulrich Drepper a écrit : On 5/20/07, Eric Dumazet <[EMAIL PROTECTED]> wrote: > 1. do nothing, always use the shared futexes. Not very attractive IMO Why do you find this non attractive ? How is it performance critical ? You should know better than any other that the problem is not that the

Re: first little problem with private futexes

On 5/20/07, Eric Dumazet <[EMAIL PROTECTED]> wrote: > 1. do nothing, always use the shared futexes. Not very attractive IMO Why do you find this non attractive ? How is it performance critical ? You should know better than any other that the problem is not that the problem itself is the onl

Re: first little problem with private futexes

Ulrich Drepper a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here's a first little issue with private futex I came across. But a real bug but a hole. When we use clone() with CLONE_CHILD_CLEARTID possible waiters are woken upon termination of the thread. This operation uses FUTEX_WA

first little problem with private futexes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here's a first little issue with private futex I came across. But a real bug but a hole. When we use clone() with CLONE_CHILD_CLEARTID possible waiters are woken upon termination of the thread. This operation uses FUTEX_WAKE so far. But it in almos