Sébastien Dugué a écrit :
FUTEX_REQUEUE is used by pthread_cond_signal to requeue the __data.__futex onto __data.__lock.You meant FUTEX_WAKE_OP, I guess. I could not find any place still using FUTEX_REQUEUE in glibc 2.4.
... FUTEX_CMP_REQUEUE ... ;-) FUTEX_REQUEUE is obsolote ... -- Pierre P. - 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/
- References:
- NPTL mutex and the scheduling priority
- From: Atsushi Nemoto <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Arjan van de Ven <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Jakub Jelinek <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Sébastien Dugué <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Jakub Jelinek <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Sébastien Dugué <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Jakub Jelinek <[email protected]>
- Re: NPTL mutex and the scheduling priority
- From: Sébastien Dugué <[email protected]>
- NPTL mutex and the scheduling priority
- Prev by Date: Re: [PATCH 2.6.17-rc6 7/9] Remove some of the kmemleak false positives
- Next by Date: loop devices removable
- Previous by thread: Re: NPTL mutex and the scheduling priority
- Next by thread: Re: NPTL mutex and the scheduling priority
- Index(es):
 |