Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1619205 > unrolled thread
| Started by | Darren Hart <dvhart@infradead.org> |
|---|---|
| First post | 2017-04-08 03:30 +0200 |
| Last post | 2017-04-08 03:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH -v6 12/13] futex: futex_unlock_pi() determinism Darren Hart <dvhart@infradead.org> - 2017-04-08 03:30 +0200
| From | Darren Hart <dvhart@infradead.org> |
|---|---|
| Date | 2017-04-08 03:30 +0200 |
| Subject | Re: [PATCH -v6 12/13] futex: futex_unlock_pi() determinism |
| Message-ID | <ttNmp-76Q-13@gated-at.bofh.it> |
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 > important. > > While in practise; given the previous patch; it will be very unlikely Heh, that's not what semicolons are for ;-) Commas here, or a parenthetical. > to ever really take more than one or two rounds, proving so becomes > rather hard. > > However, now that modifying wait_list is done while holding both > hb->lock and wait_lock, we can avoid the scenario entirely if we > acquire wait_lock while still holding hb-lock. Doing a hand-over, > without leaving a hole. Nice :) -- Darren Hart VMware Open Source Technology Center
Back to top | Article view | linux.kernel
csiph-web