linux-kernel - Re: [RFC] sched: fair: Don't update CPU frequency too frequently

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 1 Jun 2017 14:22:24 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Ingo Molnar <mingo@...hat.com>, Rafael Wysocki <rjw@...ysocki.net>,
        linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org,
        Vincent Guittot <vincent.guittot@...aro.org>,
        linux-pm@...r.kernel.org, Juri Lelli <Juri.Lelli@....com>,
        Dietmar.Eggemann@....com, Morten.Rasmussen@....com
Subject: Re: [RFC] sched: fair: Don't update CPU frequency too frequently

On Thu, Jun 01, 2017 at 05:04:27PM +0530, Viresh Kumar wrote:
> This patch relocates the call to utilization hook from
> update_cfs_rq_load_avg() to task_tick_fair().

That's not right. Consider hardware where 'setting' the DVFS is a
'cheap' MSR write, doing that once every 10ms (HZ=100) is absurd.

We spoke about this problem in Pisa, the proposed solution was having
each driver provide a cost metric and the generic code doing a max
filter over the window constructed from that cost metric.