Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1488953
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes |
| Date | 2016-09-22 16:50 +0200 |
| Message-ID | <skdu2-7CL-21@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <sjJFE-5Ct-15@gated-at.bofh.it> <sk6Vz-3tj-17@gated-at.bofh.it> <sk6Vz-3tj-15@gated-at.bofh.it> <skcoh-6Y0-1@gated-at.bofh.it> <skdu1-7CL-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 22 Sep 2016, Davidlohr Bueso wrote: > On Thu, 22 Sep 2016, Thomas Gleixner wrote: > > Also what's the reason that we can't do probabilistic spinning for > > FUTEX_WAIT and have to add yet another specialized variant of futexes? > > Where would this leave the respective FUTEX_WAKE? A nop? Probably have to > differentiate the fact that the queue was empty, but there was a spinning, > instead of straightforward returning 0. Sorry, but I really can't parse this answer. Can you folks please communicate with proper and coherent explanations instead of throwing a few gnawed off bones in my direction? Thanks, tglx
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH v2 0/5] futex: Introducing throughput-optimized futexes Waiman Long <Waiman.Long@hpe.com> - 2016-09-20 15:50 +0200
[RFC PATCH v2 2/5] futex: Rename futex_pi_state to futex_state Waiman Long <Waiman.Long@hpe.com> - 2016-09-20 15:50 +0200
[RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Waiman Long <Waiman.Long@hpe.com> - 2016-09-20 15:50 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-09-21 09:00 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Peter Zijlstra <peterz@infradead.org> - 2016-09-22 09:50 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Thomas Gleixner <tglx@linutronix.de> - 2016-09-22 15:40 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Davidlohr Bueso <dave@stgolabs.net> - 2016-09-22 16:50 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Thomas Gleixner <tglx@linutronix.de> - 2016-09-22 16:50 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Davidlohr Bueso <dave@stgolabs.net> - 2016-09-22 17:20 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Thomas Gleixner <tglx@linutronix.de> - 2016-09-22 22:50 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Davidlohr Bueso <dave@stgolabs.net> - 2016-09-22 23:40 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Thomas Gleixner <tglx@linutronix.de> - 2016-09-22 23:50 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Thomas Gleixner <tglx@linutronix.de> - 2016-09-22 22:30 +0200
Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes Peter Zijlstra <peterz@infradead.org> - 2016-09-22 15:30 +0200
[RFC PATCH v2 5/5] futex, doc: TO futexes document Waiman Long <Waiman.Long@hpe.com> - 2016-09-20 15:50 +0200
[RFC PATCH v2 4/5] futex: Add timeout support to TO futexes Waiman Long <Waiman.Long@hpe.com> - 2016-09-20 15:50 +0200
csiph-web