linux-kernel - Re: [PATCH v2 0/3] Update blocked load

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]

Message-ID: <CAKfTPtD_+UA7zM7xG43D5Aa+8E7-=0qxqPnRErE9U7_rv=uEoA@mail.gmail.com>
Date:   Tue, 6 Feb 2018 22:46:37 +0100
From:   Vincent Guittot <vincent.guittot@...aro.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Ingo Molnar <mingo@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Valentin Schneider <valentin.schneider@....com>,
        Morten Rasmussen <morten.rasmussen@...s.arm.com>,
        Brendan Jackman <brendan.jackman@....com>,
        Dietmar Eggemann <dietmar.eggemann@....com>
Subject: Re: [PATCH v2 0/3] Update blocked load

On 6 February 2018 at 22:25, Peter Zijlstra <peterz@...radead.org> wrote:
> On Tue, Feb 06, 2018 at 08:23:04PM +0100, Vincent Guittot wrote:
>> This patchset applies on top of Peter's sched/esting branch minus the last 2 commit:
>> 56eb46798b33 ("sched: Clean up nohz enter/exit")
>
> So what will update the blocked load after we wake from a total idle?
>
> I don't see anything here that would do that (yet?).

The fast wake up path uses only idle state and runnable load average.
The later is normally up to date and null ( thanks to the propagation
of runnable) because of the fact that we were totally idle.
For the other "slow" path, we need to update the utilization of the
CPUs when we use them (and the load as well even if we don't use it).
This will be part of another patch as the overhead need to be
evaluated

That should be enough to take the right decision at wake up from a
long total idle state

Then for a complete update of the load metric, we can either wait for
the next tick or kick an ilb at wake up (what you don't like).