public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Qais Yousef <qyousef@layalina.io>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Ingo Molnar <mingo@kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Christian Loehle <christian.loehle@arm.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched: Consolidate cpufreq updates
Date: Tue, 7 May 2024 10:02:30 +0200	[thread overview]
Message-ID: <20240507080230.GP40213@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240507005659.d4rzzaoq3isanndf@airbuntu>

On Tue, May 07, 2024 at 01:56:59AM +0100, Qais Yousef wrote:

> Yes. How about this? Since stopper class appears as RT, we should still check
> for this class specifically.

Much nicer!

> static inline void update_cpufreq_ctx_switch(struct rq *rq, struct task_struct *prev)
> {
> #ifdef CONFIG_CPU_FREQ
> 	if (likely(fair_policy(current->policy))) {
> 
> 		if (unlikely(current->in_iowait)) {
> 			cpufreq_update_util(rq, SCHED_CPUFREQ_IOWAIT | SCHED_CPUFREQ_FORCE_UPDATE);
> 			return;
> 		}
> 
> #ifdef CONFIG_SMP
> 		/*
> 		 * Allow cpufreq updates once for every update_load_avg() decay.
> 		 */
> 		if (unlikely(rq->cfs.decayed)) {
> 			rq->cfs.decayed = false;
> 			cpufreq_update_util(rq, 0);
> 			return;
> 		}
> #endif
> 		return;
> 	}
> 
> 	/*
> 	 * RT and DL should always send a freq update. But we can do some
> 	 * simple checks to avoid it when we know it's not necessary.
> 	 */
> 	if (task_is_realtime(current)) {
> 		if (dl_task(current) && current->dl.flags & SCHED_FLAG_SUGOV) {
> 			/* Ignore sugov kthreads, they're responding to our requests */
> 			return;
> 		}
> 
> 		if (rt_task(current) && rt_task(prev)) {

doesn't task_is_realtime() impy rt_task() ?

Also, this clause still includes DL tasks, is that okay?

> #ifdef CONFIG_UCLAMP_TASK
> 			unsigned long curr_uclamp_min = uclamp_eff_value(current, UCLAMP_MIN);
> 			unsigned long prev_uclamp_min = uclamp_eff_value(prev, UCLAMP_MIN);
> 
> 			if (curr_uclamp_min == prev_uclamp_min)
> #endif
> 				return;
> 		}
> 
> #ifdef CONFIG_SMP
> 		if (unlikely(current->sched_class == &stop_sched_class))
> 			return;
> #endif
> 
> 		cpufreq_update_util(rq, SCHED_CPUFREQ_FORCE_UPDATE);
> 		return;
> 	}
> 
> 	/* Everything else shouldn't trigger a cpufreq update */
> 	return;
> #endif
> }

  reply	other threads:[~2024-05-07  8:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05 23:31 [PATCH v2] sched: Consolidate cpufreq updates Qais Yousef
2024-05-06 10:05 ` Peter Zijlstra
2024-05-07  0:56   ` Qais Yousef
2024-05-07  8:02     ` Peter Zijlstra [this message]
2024-05-07 10:42       ` Qais Yousef
2024-05-07  8:58 ` Vincent Guittot
2024-05-07 10:21   ` Vincent Guittot
2024-05-07 11:08   ` Qais Yousef
2024-05-07 12:53     ` Vincent Guittot
2024-05-09 12:40       ` Qais Yousef
2024-05-13  8:49         ` Vincent Guittot
2024-05-11  2:03       ` Qais Yousef
2024-05-13  8:50         ` Vincent Guittot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240507080230.GP40213@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=christian.loehle@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vschneid@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox