Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1685080
| From | Juri Lelli <juri.lelli@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient |
| Date | 2017-07-11 16:40 +0200 |
| Message-ID | <u24uu-3uu-23@gated-at.bofh.it> (permalink) |
| References | <u1nSx-22T-17@gated-at.bofh.it> <u1EA2-3YQ-23@gated-at.bofh.it> <u1VKx-6zi-1@gated-at.bofh.it> <u1XCG-7G3-13@gated-at.bofh.it> <u24uu-3uu-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 11/07/17 07:33, Joel Fernandes wrote: > Hi Juri, > > On Tue, Jul 11, 2017 at 12:14 AM, Juri Lelli <juri.lelli@arm.com> wrote: > [..] > >> > Considering it a per-cpu thing, isn't enough that it gets bumped up or > >> > decayed only when a CPU does an update (by using the above from > >> > sugov_update_shared)? > >> > > >> > If we go this way I think we will only need to reset prev_iowait_boost > >> > if delta_ns > TICK_NSEC during the for_each_cpu() loop of sugov_next_ > >> > freq_shared(). > >> > > >> > >> Actually the "decay" was already being done before (without this > >> patch), I am just preserving the same old behavior where we do decay. > >> Perhaps your proposal can be a separate match? Or did I miss something > >> else subtle here? > >> > > > > True, we are currently decaying anyway. > > > > Looking again at this path made me however think if we really need to. I > > guess we need currently, as we bump frenquency to max and then decay it. > > But, with your changes, I was wondering if we can simplify the thing and > > decay only on the per-CPU update path. > > Yes that makes sense to me, but even if we're at max, we should still > benefit from your idea right? (I didn't follow why being at min makes > the idea better, I think its a good idea in both cases (whether we are > boosting to max and ramping down or starting from the min) but let me > know if I missed something) > Not better, but I thought that if we start from max and decay we probably need to have more chances to decay faster (so decaying also when aggregating request for a domain is probably needed)? > If I understand correctly what you're proposing: > 1. Remove the decay from sugov_iowait_boost > 2. Add the iowait_boost decay unconditionally to > sugov_set_iowait_boost for the !SCHED_CPUFREQ_IOWAIT case. > > That would also get rid of the prev_iowait_boost flag and simplify > things, and also address Peter's concern of adding 'bool' in composite > types :) > OK, just a suggestion however, didn't play with the idea myself, it might not work. :) Thanks, - Juri
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-09 19:10 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Juri Lelli <juri.lelli@arm.com> - 2017-07-10 13:00 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-11 07:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Juri Lelli <juri.lelli@arm.com> - 2017-07-11 09:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Juri Lelli <juri.lelli@arm.com> - 2017-07-11 16:40 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-11 16:40 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-11 12:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Peter Zijlstra <peterz@infradead.org> - 2017-07-11 13:50 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-11 16:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-11 16:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-12 07:10 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Peter Zijlstra <peterz@infradead.org> - 2017-07-12 11:40 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-12 11:50 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Peter Zijlstra <peterz@infradead.org> - 2017-07-12 15:30 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-13 05:50 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-13 04:10 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-13 05:40 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-13 06:00 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Viresh Kumar <viresh.kumar@linaro.org> - 2017-07-13 06:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Joel Fernandes <joelaf@google.com> - 2017-07-13 06:20 +0200
Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient Peter Zijlstra <peterz@infradead.org> - 2017-07-11 13:50 +0200
csiph-web