Re: [PATCH 2/4] Fix futex timeouts and handle futex error codes.
[Thread Prev] | [Thread Next]
- Subject: Re: [PATCH 2/4] Fix futex timeouts and handle futex error codes.
- From: Ori Bernstein <ori@xxxxxxxxxxxxxx>
- Reply-to: myrddin-dev@xxxxxxxxxxxxxx
- Date: Tue, 14 Aug 2018 23:39:20 -0700
- To: myrddin-dev@xxxxxxxxxxxxxx
- Cc: iriri <iri@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Tue, 14 Aug 2018 23:15:39 -0700, Ori Bernstein <ori@xxxxxxxxxxxxxx> wrote: > Looking at this code, I realized it may have lost something > in the translation from Linux cond vars. Isn't it possible > that if we have multiple waiters on the condition variable, > we could miss waking up a waiter, because we erronously decide > a lock is uncontended? > Never mind, I'm wrong. This isn't a problem, since the next signal will wake up the next guy. The only case where we need to set the state to contended is when doing a broadcast. -- Ori Bernstein
[PATCH 2/4] Fix futex timeouts and handle futex error codes. | iriri <iri@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
Re: [PATCH 2/4] Fix futex timeouts and handle futex error codes. | Ori Bernstein <ori@xxxxxxxxxxxxxx> |
- Prev by Date: Re: [PATCH 2/4] Fix futex timeouts and handle futex error codes.
- Next by Date: Re: What IRC network does Myrddin use?
- Previous by thread: Re: [PATCH 2/4] Fix futex timeouts and handle futex error codes.
- Next by thread: [PATCH 2/4] Fix futex timeouts and handle futex error codes.
- Index(es):