linux-kernel - Re: [PATCH] arm64: defconfig: enable CONFIG_SCHED

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: <cb383a76-8848-44cd-6f32-fd30478d9ebd@gentwo.org>
Date: Tue, 12 Aug 2025 09:33:07 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Jeremy Linton <jeremy.linton@....com>
cc: Huang Shijie <shijie@...amperecomputing.com>, catalin.marinas@....com, 
    will@...nel.org, patches@...erecomputing.com, 
    Shubhang@...amperecomputing.com, krzysztof.kozlowski@...aro.org, 
    bjorn.andersson@....qualcomm.com, geert+renesas@...der.be, arnd@...db.de, 
    nm@...com, ebiggers@...nel.org, nfraprado@...labora.com, 
    prabhakar.mahadev-lad.rj@...renesas.com, 
    linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: defconfig: enable CONFIG_SCHED_CLUSTER

On Mon, 11 Aug 2025, Jeremy Linton wrote:

> From what I've seen, SCHED_CLUSTER seems to be a bit of give and take
> depending on benchmark and machine. I'm not sure if it should be default
> enabled or not, but it would really be nice to have at least a larger sweep of
> benchmarks/machines in order to be sure of the decision.

If the hardware provides a clusterid then I think this clusterid should be
used for the sched domains. CONFIG_SCHED_CLUSTER does that. So it should
be the default.

If there is no cluster information then these domains should not be
created. I think that is already the case?