[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <415e4351-10b3-4134-ad11-8dd1cda037f1@amperemail.onmicrosoft.com>
Date: Tue, 12 Aug 2025 11:05:49 +0800
From: Shijie Huang <shijie@...eremail.onmicrosoft.com>
To: Jeremy Linton <jeremy.linton@....com>,
Huang Shijie <shijie@...amperecomputing.com>, catalin.marinas@....com,
will@...nel.org
Cc: patches@...erecomputing.com, cl@...ux.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,
Christoph Lameter <cl@...two.org>
Subject: Re: [PATCH] arm64: defconfig: enable CONFIG_SCHED_CLUSTER
On 11/08/2025 23:13, Jeremy Linton wrote:
> Hi,
>
> On 8/7/25 9:55 PM, Huang Shijie wrote:
>> In the server, if some workload which will create lot of
>> tasks, and will have many task migrations, we can get better
>> performance when we enable the CONFIG_SCHED_CLUSTER.
>>
>> For example, the Specjbb may have better performance:
>> Critical-jops : 26%
>> Max-jops : 7%
>>
>> So enable it by default.
>
> 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.
Yes, I agree.
Maybe I should create a patch only enable SCHED_CLUSTER for Ampere's
machine.
Thanks
>
>
Powered by blists - more mailing lists