Re: [PATCH -v6 12/13] futex: futex_unlock_pi() determinism

2017-04-07 Thread Darren Hart
On Wed, Mar 22, 2017 at 11:35:59AM +0100, Peter Zijlstra wrote: > The problem with returning -EAGAIN when the waiter state mismatches is > that it becomes very hard to proof a bounded execution time on the prove > operation. And seeing that this is a RT operation, this is somewhat an RT >

Re: [PATCH -v6 12/13] futex: futex_unlock_pi() determinism

2017-04-07 Thread Darren Hart
On Wed, Mar 22, 2017 at 11:35:59AM +0100, Peter Zijlstra wrote: > The problem with returning -EAGAIN when the waiter state mismatches is > that it becomes very hard to proof a bounded execution time on the prove > operation. And seeing that this is a RT operation, this is somewhat an RT >

[PATCH -v6 12/13] futex: futex_unlock_pi() determinism

2017-03-22 Thread Peter Zijlstra
The problem with returning -EAGAIN when the waiter state mismatches is that it becomes very hard to proof a bounded execution time on the operation. And seeing that this is a RT operation, this is somewhat important. While in practise; given the previous patch; it will be very unlikely to ever

[PATCH -v6 12/13] futex: futex_unlock_pi() determinism

2017-03-22 Thread Peter Zijlstra
The problem with returning -EAGAIN when the waiter state mismatches is that it becomes very hard to proof a bounded execution time on the operation. And seeing that this is a RT operation, this is somewhat important. While in practise; given the previous patch; it will be very unlikely to ever