linux-kernel - Re: [RFC PATCH 6/6 v8] sched/fair: Add EAS and idle cpu push trigger

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] [day] [month] [year] [list]

Message-ID: <20260211005955.2aqc44be5wlk6nrb@airbuntu>
Date: Wed, 11 Feb 2026 00:59:55 +0000
From: Qais Yousef <qyousef@...alina.io>
To: Vincent Guittot <vincent.guittot@...aro.org>
Cc: mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
	dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
	mgorman@...e.de, vschneid@...hat.com, linux-kernel@...r.kernel.org,
	pierre.gondois@....com, kprateek.nayak@....com,
	hongyan.xia2@....com, christian.loehle@....com,
	luis.machado@....com
Subject: Re: [RFC PATCH 6/6 v8] sched/fair: Add EAS and idle cpu push trigger

On 02/09/26 14:20, Vincent Guittot wrote:

> >
> > > +     util = max(task_util_est(p), task_runnable(p));
> >
> > We must take the min(util, SCHED_CAPACITY_SCALE) here since runnable can get
> > too large making the condition above true even if you are on the biggest
> > capacity cpu.
> 
> hmm task_runnable should not go above SCHED_CAPACITY_SCALE. do you
> have seen cases where task's runnable_avg goes above
> SCHED_CAPACITY_SCALE ?
> 
> In fact neither task_util_est nor task_runnable should go above
> SCHED_CAPACITY_SCALE

Yes you're right. My memory is hazy now, but I recall I've seen runnable_avg
jump above 1024, but that might have been load_avg.