[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bfa0628-bd74-47c3-ba3c-4724acbfd717@arm.com>
Date: Fri, 21 Jun 2024 12:40:58 +0200
From: Dietmar Eggemann <dietmar.eggemann@....com>
To: Xuewen Yan <xuewen.yan94@...il.com>, Qais Yousef <qyousef@...alina.io>
Cc: Xuewen Yan <xuewen.yan@...soc.com>, vincent.guittot@...aro.org,
mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com, vincent.donnefort@....com,
ke.wang@...soc.com, linux-kernel@...r.kernel.org, christian.loehle@....com
Subject: Re: [PATCH] sched/fair: Prevent cpu_busy_time from exceeding
actual_cpu_capacity
On 19/06/2024 04:46, Xuewen Yan wrote:
> On Tue, Jun 18, 2024 at 10:58 PM Qais Yousef <qyousef@...alina.io> wrote:
>>
>> On 06/17/24 12:03, Qais Yousef wrote:
[...]
> Sorry for the late reply...
> In our own tree, we removed the check for rd overutil in feec(), so
> the above case often occurs.
How to you schedule hackbench on this thing then? Via EAS or do you just
exclude this kind of workload?
> And now it seems that on the mainline, uclamp_max is the only way to
> override this.
[...]
Powered by blists - more mailing lists