linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Wanpeng Li <kernellwp@gmail.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, Wanpeng Li <wanpeng.li@hotmail.com>,
	Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v3] sched/cpufreq: optimize cpufreq update kicker to avoid update multiple times
Date: Fri, 22 Apr 2016 14:04:56 +0200	[thread overview]
Message-ID: <571A1368.9060409@intel.com> (raw)
In-Reply-To: <1461316044-9520-1-git-send-email-wanpeng.li@hotmail.com>

[Added linux-pm to the CC - can you please do so for PM-related patches 
in the future?]

On 4/22/2016 11:07 AM, Wanpeng Li wrote:
> From: Wanpeng Li <wanpeng.li@hotmail.com>
>
> Sometimes delta_exec is 0 due to update_curr() is called multiple times,
> this is captured by:
>
> 	u64 delta_exec = rq_clock_task(rq) - curr->se.exec_start;
>
> This patch optimizes the cpufreq update kicker by bailing out when nothing
> changed, it will benefit the upcoming schedutil, since otherwise it will
> (over)react to the special util/max combination.
>
> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>

The changelog looks better now, thanks!

Peter, do I think correctly that you're going to take care of this one?  
Or do you want me to take it?

> ---
> v1 -> v2:
>   * add From: head
> v2 -> v3:
>   * update changelog
>
>   kernel/sched/deadline.c | 8 ++++----
>   kernel/sched/rt.c       | 8 ++++----
>   2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index affd97e..8f9b5af 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -717,10 +717,6 @@ static void update_curr_dl(struct rq *rq)
>   	if (!dl_task(curr) || !on_dl_rq(dl_se))
>   		return;
>   
> -	/* Kick cpufreq (see the comment in linux/cpufreq.h). */
> -	if (cpu_of(rq) == smp_processor_id())
> -		cpufreq_trigger_update(rq_clock(rq));
> -
>   	/*
>   	 * Consumed budget is computed considering the time as
>   	 * observed by schedulable tasks (excluding time spent
> @@ -736,6 +732,10 @@ static void update_curr_dl(struct rq *rq)
>   		return;
>   	}
>   
> +	/* kick cpufreq (see the comment in linux/cpufreq.h). */
> +	if (cpu_of(rq) == smp_processor_id())
> +		cpufreq_trigger_update(rq_clock(rq));
> +
>   	schedstat_set(curr->se.statistics.exec_max,
>   		      max(curr->se.statistics.exec_max, delta_exec));
>   
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index c41ea7a..19e1306 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -953,14 +953,14 @@ static void update_curr_rt(struct rq *rq)
>   	if (curr->sched_class != &rt_sched_class)
>   		return;
>   
> -	/* Kick cpufreq (see the comment in linux/cpufreq.h). */
> -	if (cpu_of(rq) == smp_processor_id())
> -		cpufreq_trigger_update(rq_clock(rq));
> -
>   	delta_exec = rq_clock_task(rq) - curr->se.exec_start;
>   	if (unlikely((s64)delta_exec <= 0))
>   		return;
>   
> +	/* Kick cpufreq (see the comment in linux/cpufreq.h). */
> +	if (cpu_of(rq) == smp_processor_id())
> +		cpufreq_trigger_update(rq_clock(rq));
> +
>   	schedstat_set(curr->se.statistics.exec_max,
>   		      max(curr->se.statistics.exec_max, delta_exec));
>   

  reply	other threads:[~2016-04-22 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22  9:07 [PATCH v3] sched/cpufreq: optimize cpufreq update kicker to avoid update multiple times Wanpeng Li
2016-04-22 12:04 ` Rafael J. Wysocki [this message]
2016-04-25 14:31   ` Peter Zijlstra
2016-04-28 10:26 ` [tip:sched/core] sched/cpufreq: Optimize " tip-bot for Wanpeng Li

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=571A1368.9060409@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=kernellwp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=wanpeng.li@hotmail.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;
as well as URLs for NNTP newsgroup(s).