Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1619160
| From | Darren Hart <dvhart@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH -v6 10/13] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock() |
| Date | 2017-04-08 01:40 +0200 |
| Message-ID | <ttLDX-5Wh-3@gated-at.bofh.it> (permalink) |
| References | <tnM01-11I-7@gated-at.bofh.it> <tnM02-11I-11@gated-at.bofh.it> <ttLDX-5Wh-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Apr 07, 2017 at 04:30:59PM -0700, Darren Hart wrote: > On Wed, Mar 22, 2017 at 11:35:57AM +0100, Peter Zijlstra wrote: > > With the ultimate goal of keeping rt_mutex wait_list and futex_q > > waiters consistent we want to split 'rt_mutex_futex_lock()' into finer > > I want to be clear that I understand why this patch is needed - as it actually > moves both the waiter removal and the rt_waiter freeing under the hb lock while > you've been working to be less dependent on the hb lock. > > Was inconsistency of the rt_mutex wait_list and the futex_q waiters a problem > before this patch series, or do the previous patches make this one necessary? Ah, this is a follow-on to the issue described in 7 of 10. Nevermind. -- Darren Hart VMware Open Source Technology Center
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH -v6 10/13] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock() Darren Hart <dvhart@infradead.org> - 2017-04-08 01:40 +0200
csiph-web