[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc525124-da79-45af-a99b-ec4616b3fa6b@arm.com>
Date: Fri, 8 Dec 2023 10:05:38 +0000
From: Lukasz Luba <lukasz.luba@....com>
To: Qais Yousef <qyousef@...alina.io>
Cc: linux-kernel@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
linux-pm@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
Wei Wang <wvw@...gle.com>, Rick Yiu <rickyiu@...gle.com>,
Chung-Kai Mei <chungkai@...gle.com>,
Hongyan Xia <hongyan.xia2@....com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 1/4] sched/fair: Be less aggressive in calling
cpufreq_update_util()
Hi Qais,
On 12/8/23 01:52, Qais Yousef wrote:
[snip]
> @@ -6704,14 +6677,6 @@ enqueue_task_fair(struct rq *rq, struct task_struct *p, int flags)
> */
> util_est_enqueue(&rq->cfs, p);
>
> - /*
> - * If in_iowait is set, the code below may not trigger any cpufreq
> - * utilization updates, so do it here explicitly with the IOWAIT flag
> - * passed.
> - */
> - if (p->in_iowait)
> - cpufreq_update_util(rq, SCHED_CPUFREQ_IOWAIT);
> -
Why this io wait boost is considered as the $subject says 'aggressive'
calling?
Regards,
Lukasz
Powered by blists - more mailing lists