Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1526593

Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits
Date 2016-11-21 12:50 +0100
Message-ID <sFVgJ-C3-9@gated-at.bofh.it> (permalink)
References (1 earlier) <sFTHY-8fb-37@gated-at.bofh.it> <sFTRD-8lZ-23@gated-at.bofh.it> <sFUkF-8vE-19@gated-at.bofh.it> <sFUNI-sG-7@gated-at.bofh.it> <sFV73-yJ-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, Nov 21, 2016 at 05:00:16PM +0530, Viresh Kumar wrote:
> On 21-11-16, 12:12, Peter Zijlstra wrote:
> > I think it should be replaced by a value provided by the driver. It
> > makes sense to have a rate-limit in so far as that it doesn't make sense
> > to try and program the hardware faster than it can actually change
> > frequencies and/or have a programming cost amortization. And this very
> > clearly is a driver specific thing.
> 
> We already have something called as transition_latency for that (though it isn't
> used much currently).
> 
> > It however doesn't make sense to me to fudge with this in order to
> > achieve ramp up/down differences.
> 
> So if a platform, for example, can do DVFS in say 100-500 us, then the scheduler
> should try to re-evaluate frequency (and update it) after that short of a
> period? Wouldn't that scheme waste lots of time doing just freq updates? And
> that's the primary reason why cpufreq governors have some sort of sampling-rate
> or rate-limit until now.

Dunno.. there's of course the cost amortization, but by the time we've
reached sugov_should_update_freq() most of the 'expensive' parts have
already been done from the scheduler's POV and its once again down to
the driver.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] cpufreq: schedutil: add up/down frequency transition rate limits Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-17 06:30 +0100
  Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-21 11:10 +0100
    Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 11:20 +0100
      Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-21 11:50 +0100
        Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 12:20 +0100
          Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-21 12:40 +0100
            Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 12:50 +0100
      Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Juri Lelli <Juri.Lelli@arm.com> - 2016-11-21 13:20 +0100
        Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 13:30 +0100
          Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Juri Lelli <Juri.Lelli@arm.com> - 2016-11-21 15:00 +0100
            Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 15:20 +0100
              Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Juri Lelli <Juri.Lelli@arm.com> - 2016-11-21 15:40 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 15:50 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Juri Lelli <Juri.Lelli@arm.com> - 2016-11-21 16:00 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits Vincent Guittot <vincent.guittot@linaro.org> - 2016-11-22 10:30 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Patrick Bellasi <patrick.bellasi@arm.com> - 2016-11-22 12:10 +0100
            Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Patrick Bellasi <patrick.bellasi@arm.com> - 2016-11-21 16:00 +0100
              Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 16:30 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 16:40 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Patrick Bellasi <patrick.bellasi@arm.com> - 2016-11-21 17:30 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition  rate limits Peter Zijlstra <peterz@infradead.org> - 2016-11-21 17:50 +0100
                Re: [PATCH] cpufreq: schedutil: add up/down frequency transition rate limits "Rafael J. Wysocki" <rafael@kernel.org> - 2016-11-21 22:00 +0100

csiph-web