This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] mutex destruction (#13690): problem description and workarounds
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Thu, 27 Nov 2014 11:55:15 -0500
- Subject: Re: [RFC] mutex destruction (#13690): problem description and workarounds
- Authentication-results: sourceware.org; auth=none
- References: <1396621230 dot 10643 dot 7191 dot camel at triegel dot csb> <54762514 dot 2030301 at redhat dot com> <1417086669 dot 1771 dot 237 dot camel at triegel dot csb>
On 11/27/2014 06:11 AM, Torvald Riegel wrote:
> One thing that is missing in my description of this workaround is that
> we probably need a new FUTEX_WAIT_SPURIOUS syscall as well, so that we
> can distinguish not only spurious from non-spurious wake calls, but only
> those waiters that can tolerate spurious wake-ups from those that
> cannot.
I'm fine with that also.
I still think option 2 is the best and has the most chance of success.
Cheers,
Carlos.