From: Patrick Bellasi <patrick.bellasi@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@arm.com>,
Joel Fernandes <joelaf@google.com>,
Andres Oportus <andresoportus@google.com>,
Todd Kjos <tkjos@android.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steve Muckle <smuckle.linux@gmail.com>,
Brendan Jackman <brendan.jackman@arm.com>
Subject: Re: [PATCH v2 3/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks
Date: Wed, 5 Jul 2017 14:41:26 +0100 [thread overview]
Message-ID: <20170705134126.GD2659@e110439-lin> (raw)
In-Reply-To: <20170705060136.GO3532@vireshk-i7>
[+Brendan]
On 05-Jul 11:31, Viresh Kumar wrote:
> On 04-07-17, 18:34, Patrick Bellasi wrote:
> > diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> > index 004ae18..98704d8 100644
> > --- a/kernel/sched/cpufreq_schedutil.c
> > +++ b/kernel/sched/cpufreq_schedutil.c
> > @@ -216,6 +216,7 @@ static void sugov_update_single(struct update_util_data *hook, u64 time,
> > struct cpufreq_policy *policy = sg_policy->policy;
> > unsigned long util, max;
> > unsigned int next_f;
> > + bool rt_mode;
> > bool busy;
> >
> > /* Skip updates generated by sugov kthreads */
> > @@ -230,7 +231,15 @@ static void sugov_update_single(struct update_util_data *hook, u64 time,
> >
> > busy = sugov_cpu_is_busy(sg_cpu);
> >
> > - if (flags & SCHED_CPUFREQ_RT_DL) {
> > + /*
> > + * While RT/DL tasks are running we do not want FAIR tasks to
> > + * overvrite this CPU's flags, still we can update utilization and
> > + * frequency (if required/possible) to be fair with these tasks.
> > + */
> > + rt_mode = task_has_dl_policy(current) ||
> > + task_has_rt_policy(current) ||
> > + (flags & SCHED_CPUFREQ_RT_DL);
>
> We may want to create a separate inline function for above, as it is already
> used twice in this patch.
Good idea.
> But I was wondering if we can get some help from the scheduler to avoid such
> code here. I understand that we don't want to do the aggregation in the
> scheduler to keep it clean and keep such governor specific thing here.
Indeed.
> But what about clearing the sched-class's flag from .pick_next_task() callback
> when they return NULL ?
>
> What about something like this instead (completely untested), with which we
> don't need the 2/3 patch as well:
Just had a fast check but I think something like that can work.
We had an internal discussion with Brendan (in CC now) which had a
similar proposal.
Main counter arguments for me was:
1. we wanna to reduce the pollution of scheduling classes code with
schedutil specific code, unless strictly necessary
2. we never had a "clear bit" semantics for flags updates
Thus this proposal seemed to me less of a discontinuity wrt the
current interface. However, something similar to what you propose
below should also work. Let's collect some more feedback...
> diff --git a/include/linux/sched/cpufreq.h b/include/linux/sched/cpufreq.h
> index d2be2ccbb372..e81a6b5591f5 100644
> --- a/include/linux/sched/cpufreq.h
> +++ b/include/linux/sched/cpufreq.h
> @@ -11,6 +11,10 @@
> #define SCHED_CPUFREQ_DL (1U << 1)
> #define SCHED_CPUFREQ_IOWAIT (1U << 2)
>
> +#define SCHED_CPUFREQ_CLEAR (1U << 31)
> +#define SCHED_CPUFREQ_CLEAR_RT (SCHED_CPUFREQ_CLEAR | SCHED_CPUFREQ_RT)
> +#define SCHED_CPUFREQ_CLEAR_DL (SCHED_CPUFREQ_CLEAR | SCHED_CPUFREQ_DL)
> +
> #define SCHED_CPUFREQ_RT_DL (SCHED_CPUFREQ_RT | SCHED_CPUFREQ_DL)
>
> #ifdef CONFIG_CPU_FREQ
> diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> index 076a2e31951c..f32e15d59d62 100644
> --- a/kernel/sched/cpufreq_schedutil.c
> +++ b/kernel/sched/cpufreq_schedutil.c
> @@ -218,6 +218,9 @@ static void sugov_update_single(struct update_util_data *hook, u64 time,
> unsigned int next_f;
> bool busy;
>
> + if (flags & SCHED_CPUFREQ_CLEAR)
> + return;
Here we should still clear the flags, like what we do for the shared
case... just to keep the internal status consiste with the
notifications we have got from the scheduling classes.
> +
> sugov_set_iowait_boost(sg_cpu, time, flags);
> sg_cpu->last_update = time;
>
> @@ -296,7 +299,13 @@ static void sugov_update_shared(struct update_util_data *hook, u64 time,
>
> sg_cpu->util = util;
> sg_cpu->max = max;
> - sg_cpu->flags = flags;
> +
> + if (unlikely(flags & SCHED_CPUFREQ_CLEAR)) {
> + sg_cpu->flags &= ~(flags & ~SCHED_CPUFREQ_CLEAR);
> + return;
> + }
> +
> + sg_cpu->flags |= flags;
>
> sugov_set_iowait_boost(sg_cpu, time, flags);
> sg_cpu->last_update = time;
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index a2ce59015642..441d6153d654 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -1203,8 +1203,10 @@ pick_next_task_dl(struct rq *rq, struct task_struct *prev, struct rq_flags *rf)
> if (prev->sched_class == &dl_sched_class)
> update_curr_dl(rq);
>
> - if (unlikely(!dl_rq->dl_nr_running))
> + if (unlikely(!dl_rq->dl_nr_running)) {
> + cpufreq_update_this_cpu(rq, SCHED_CPUFREQ_CLEAR_DL);
> return NULL;
> + }
>
> put_prev_task(rq, prev);
>
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index 979b7341008a..bca9e4bb7ec4 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -1556,8 +1556,10 @@ pick_next_task_rt(struct rq *rq, struct task_struct *prev, struct rq_flags *rf)
> if (prev->sched_class == &rt_sched_class)
> update_curr_rt(rq);
>
> - if (!rt_rq->rt_queued)
> + if (!rt_rq->rt_queued) {
> + cpufreq_update_this_cpu(rq, SCHED_CPUFREQ_CLEAR_RT);
> return NULL;
> + }
>
> put_prev_task(rq, prev);
>
> --
> viresh
--
#include <best/regards.h>
Patrick Bellasi
next prev parent reply other threads:[~2017-07-05 13:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 17:34 [PATCH v2 0/6] cpufreq: schedutil: fixes for flags updates Patrick Bellasi
2017-07-04 17:34 ` [PATCH v2 1/6] cpufreq: schedutil: ignore sugov kthreads Patrick Bellasi
2017-07-05 5:00 ` Viresh Kumar
2017-07-05 11:38 ` Patrick Bellasi
2017-07-06 4:50 ` Viresh Kumar
2017-07-06 22:18 ` Rafael J. Wysocki
2017-07-11 19:08 ` Saravana Kannan
2017-07-04 17:34 ` [PATCH v2 2/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter Patrick Bellasi
2017-07-05 4:50 ` Viresh Kumar
2017-07-05 13:04 ` Patrick Bellasi
2017-07-06 5:46 ` Viresh Kumar
2017-07-07 4:43 ` Joel Fernandes
2017-07-07 10:17 ` Juri Lelli
2017-07-11 19:16 ` Saravana Kannan
2017-07-04 17:34 ` [PATCH v2 3/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks Patrick Bellasi
2017-07-05 6:01 ` Viresh Kumar
2017-07-05 13:41 ` Patrick Bellasi [this message]
2017-07-06 5:56 ` Viresh Kumar
2017-07-07 5:26 ` Joel Fernandes
2017-07-04 17:34 ` [PATCH v2 4/6] cpufreq: schedutil: update CFS util only if used Patrick Bellasi
2017-07-07 5:58 ` Joel Fernandes
2017-07-07 6:44 ` Vikram Mulukutla
2017-07-08 6:14 ` Joel Fernandes
2017-07-10 17:49 ` Vikram Mulukutla
2017-07-11 5:19 ` Joel Fernandes
2017-07-04 17:34 ` [PATCH v2 5/6] sched/rt: fast switch to maximum frequency when RT tasks are scheduled Patrick Bellasi
2017-07-04 17:34 ` [PATCH v2 6/6] cpufreq: schedutil: relax rate-limiting while running RT/DL tasks Patrick Bellasi
2017-07-06 22:26 ` [PATCH v2 0/6] cpufreq: schedutil: fixes for flags updates Rafael J. Wysocki
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=20170705134126.GD2659@e110439-lin \
--to=patrick.bellasi@arm.com \
--cc=andresoportus@google.com \
--cc=brendan.jackman@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=smuckle.linux@gmail.com \
--cc=tkjos@android.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/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).