Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1720747
| From | Mike Galbraith <efault@gmx.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag |
| Date | 2017-08-27 08:10 +0200 |
| Message-ID | <uiYVH-3JY-3@gated-at.bofh.it> (permalink) |
| References | <uiUfn-nC-1@gated-at.bofh.it> <uiYCl-3nF-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, 2017-08-27 at 07:44 +0200, Mike Galbraith wrote: > On Sat, 2017-08-26 at 18:02 -0700, Joel Fernandes wrote: > > Binder (Android's IPC mechanism) which uses sync wake ups during synchronous > > transactions to the scheduler to indicate that the waker is about to sleep > > soon. The current wake up path can improved when the sync flag is passed > > resulting in higher binder performance. In this patch we more strongly wake up > > the wakee on the waker's CPU if sync is passed based on a few other conditions > > such as wake_cap, cpus allowed. wake_wide is checked only after the sync flag > > check so that it doesn't mess up sync. Binder throughput tests see good > > improvement improvement when waking up wakee (calling thread) on the waker's > > CPU (called thread) with this flag. Some tests results are below: > > Sync is not a contract, it's a hint. If you really want sync behavior, > you need to create a contract signed in blood to signal that you really > really are passing the baton. P.S. to get the most bang for your synchronous buck, you want a preemptive wakeup.. but that butts heads with the fair engine. -Mike
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Joel Fernandes <joelaf@google.com> - 2017-08-27 03:10 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-27 07:50 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-27 08:10 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Joel Fernandes <joelaf@google.com> - 2017-08-27 08:40 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-27 09:20 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-27 20:10 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Joel Fernandes <joelaf@google.com> - 2017-08-28 07:30 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-28 08:20 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-28 08:50 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Joel Fernandes <joelaf@google.com> - 2017-08-28 18:30 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-28 19:20 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Joel Fernandes <joelaf@google.com> - 2017-08-27 08:30 +0200
Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag Mike Galbraith <efault@gmx.de> - 2017-08-27 09:00 +0200
csiph-web