linux-kernel - Re: [PATCH v4] Sched/fair: Block nohz tick

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: <20230703141056.GA67396@lorien.usersys.redhat.com>
Date:   Mon, 3 Jul 2023 10:10:56 -0400
From:   Phil Auld <pauld@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     linux-kernel@...r.kernel.org, Juri Lelli <juri.lelli@...hat.com>,
        Ingo Molnar <mingo@...hat.com>,
        Daniel Bristot de Oliveira <bristot@...hat.com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Valentin Schneider <vschneid@...hat.com>,
        Ben Segall <bsegall@...gle.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Mel Gorman <mgorman@...e.de>,
        Frederic Weisbecker <frederic@...nel.org>
Subject: Re: [PATCH v4] Sched/fair: Block nohz tick_stop when cfs bandwidth
 in use

On Mon, Jul 03, 2023 at 02:10:09PM +0200 Peter Zijlstra wrote:
> On Fri, Jun 30, 2023 at 12:29:10PM -0400, Phil Auld wrote:
> 
> > I think you are agreeing that I need the pick next code but need to remove
> > the hierarchy walks, right?
> 
> Yeah, the dequeue case makes we have to care about pick, not sure we
> then also need to care about sched_update_tick_dependency() though.
> There is indeed a window where these two will 'race', but afaict it is
> benign.
> 

Hm, that's confusing.

As I see it it's the enqueue case (0->1 mostly) where we need the check
in pick.  At that point in enqueue we only have a handle on ->curr which
is the idle thread.

For the dequeue case (2->1) we need the check in the
sched_update_tick_dependency() path because if the 1 is the task on the
cpu (and is staying there) then we'd otherwise clear the bit when we
shouldn't (since we aren't going to go back through pick).

I'm thinking that I'll try to set the bit in pick since we only care about
it when it's the task on the cpu.  That, I think, will simplify the
code needed to update the bit when the quota is changed (to or from
RUNTIME_INF).

Setting the bit in enqueue/dequeue means updating it on all the queued
task if it changes. Although I may clear it in dequeue just to not leave
it around stale.

Cheers,
Phil
--