linux-kernel - Re: [PATCH v4 1/3] sched/fair: allow disabling sched_balance_newidle with sched_relax_domain

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 for Android: free password hash cracker in your pocket

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

Message-ID: <xhsmhttjg6w55.mognet@vschneid-thinkpadt14sgen2i.remote.csb>
Date: Thu, 02 May 2024 18:01:10 +0200
From: Valentin Schneider <vschneid@...hat.com>
To: Vitalii Bursov <vitaly@...sov.com>, Ingo Molnar <mingo@...hat.com>,
 Peter Zijlstra <peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>,
 Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann
 <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>, Ben
 Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, Daniel Bristot
 de Oliveira <bristot@...hat.com>, linux-kernel@...r.kernel.org, Vitalii
 Bursov <vitaly@...sov.com>, Shrikanth Hegde <sshegde@...ux.ibm.com>
Subject: Re: [PATCH v4 1/3] sched/fair: allow disabling
 sched_balance_newidle with sched_relax_domain_level

On 30/04/24 18:05, Vitalii Bursov wrote:
> Change relax_domain_level checks so that it would be possible
> to include or exclude all domains from newidle balancing.
>
> This matches the behavior described in the documentation:
>   -1   no request. use system default or follow request of others.
>    0   no search.
>    1   search siblings (hyperthreads in a core).
>
> "2" enables levels 0 and 1, level_max excludes the last (level_max)
> level, and level_max+1 includes all levels.
>
> Fixes: 1d3504fcf560 ("sched, cpuset: customize sched domains, core")
> Signed-off-by: Vitalii Bursov <vitaly@...sov.com>
> Reviewed-by: Vincent Guittot <vincent.guittot@...aro.org>
> Tested-by: Dietmar Eggemann <dietmar.eggemann@....com>

Reviewed-by: Valentin Schneider <vschneid@...hat.com>