mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Joel Fernandes <joelaf@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Juri Lelli <juri.lelli@arm.com>,
	Patrick Bellasi <patrick.bellasi@arm.com>,
	Andres Oportus <andresoportus@google.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Len Brown <lenb@kernel.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH RFC v5] cpufreq: schedutil: Make iowait boost more energy efficient
Date: Thu, 20 Jul 2017 09:11:48 +0530	[thread overview]
Message-ID: <20170720034148.GI352@vireshk-i7> (raw)
In-Reply-To: <CAJWu+ooAJOCofKdqKTKe=eO7TPURtSjcDQvUUZdzs+N5h38mgQ@mail.gmail.com>

On 19-07-17, 19:38, Joel Fernandes wrote:
> On Tue, Jul 18, 2017 at 11:19 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 18-07-17, 21:39, Joel Fernandes wrote:
> >> Not really, to me B will still work because in the case the flag is
> >> set, we are correctly double boosting in the next cycle.
> >>
> >> Taking an example, with B = flag is set and D = flag is not set
> >>
> >> F = Fmin (minimum)
> >>
> >> iowait flag       B  B    B    D    D    D
> >> resulting boost   F  2*F  4*F  4*F  2*F  F
> >
> > What about this ?
> >
> > iowait flag       B  D    B    D    B    D
> > resulting boost   F  2*F  F    2*F  F    2*F
> 
> Yes I guess so but this oscillation can still happen in current code I think.

How ?

> > diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> > index 45fcf21ad685..ceac5f72d8da 100644
> > --- a/kernel/sched/cpufreq_schedutil.c
> > +++ b/kernel/sched/cpufreq_schedutil.c
> > @@ -53,6 +53,7 @@ struct sugov_cpu {
> >         struct update_util_data update_util;
> >         struct sugov_policy *sg_policy;
> >
> > +       bool iowait_boost_pending;
> >         unsigned long iowait_boost;
> >         unsigned long iowait_boost_max;
> >         u64 last_update;
> > @@ -169,7 +170,17 @@ static void sugov_set_iowait_boost(struct sugov_cpu *sg_cpu, u64 time,
> >                                    unsigned int flags)
> >  {
> >         if (flags & SCHED_CPUFREQ_IOWAIT) {
> > -               sg_cpu->iowait_boost = sg_cpu->iowait_boost_max;
> > +               if (sg_cpu->iowait_boost_pending)
> > +                       return;
> > +
> > +               sg_cpu->iowait_boost_pending = true;
> > +
> > +               if (sg_cpu->iowait_boost) {
> > +                       sg_cpu->iowait_boost = min(sg_cpu->iowait_boost << 1,
> > +                                                  sg_cpu->iowait_boost_max);
> > +               } else {
> > +                       sg_cpu->iowait_boost = sg_cpu->sg_policy->policy->min;
> > +               }
> 
> I would prefer this to be:
> 
>       if (sg_cpu->iowait_boost >= policy->min) {
>           // double it
>       } else {
>           // set it to min
>       }
> 
> This is for the case when boost happens all the way, then its capped
> at max, but when its decayed back, its not exactly decayed to Fmin but
> lower than it, so in that case when boost next time we start from
> Fmin.

Actually you can add another patch first which makes iowait_boost as 0
when it goes below min as that problem exists today as well.

And this patch would be fine then as is ?

> >         } else if (sg_cpu->iowait_boost) {
> >                 s64 delta_ns = time - sg_cpu->last_update;
> >
> > @@ -182,17 +193,23 @@ static void sugov_set_iowait_boost(struct sugov_cpu *sg_cpu, u64 time,
> >  static void sugov_iowait_boost(struct sugov_cpu *sg_cpu, unsigned long *util,
> >                                unsigned long *max)
> >  {
> > -       unsigned long boost_util = sg_cpu->iowait_boost;
> > -       unsigned long boost_max = sg_cpu->iowait_boost_max;
> > +       unsigned long boost_util, boost_max;
> >
> > -       if (!boost_util)
> > +       if (!sg_cpu->iowait_boost)
> >                 return;
> >
> > +       if (sg_cpu->iowait_boost_pending)
> > +               sg_cpu->iowait_boost_pending = false;
> > +       else
> > +               sg_cpu->iowait_boost >>= 1;
> > +
> > +       boost_util = sg_cpu->iowait_boost;
> > +       boost_max = sg_cpu->iowait_boost_max;
> > +
> >         if (*util * boost_max < *max * boost_util) {
> >                 *util = boost_util;
> >                 *max = boost_max;
> 
> This looks good to me and is kind of what I had in mind. I can spend
> some time testing it soon. Just to be clear if I were to repost this
> patch after testing, should I have your authorship and my tested-by or
> do you prefer something else?

You can keep your authorship I wouldn't mind. Maybe a suggested-by at
max would be fine.

-- 
viresh

  reply	other threads:[~2017-07-20  3:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16  8:04 Joel Fernandes
2017-07-17  8:04 ` Viresh Kumar
2017-07-17 17:35   ` Joel Fernandes
2017-07-18  5:45     ` Viresh Kumar
2017-07-18 14:02       ` Juri Lelli
2017-07-19  5:37         ` Viresh Kumar
2017-07-19  6:12           ` Joel Fernandes
2017-07-19  4:39       ` Joel Fernandes
2017-07-19  6:19         ` Viresh Kumar
2017-07-20  2:38           ` Joel Fernandes
2017-07-20  3:41             ` Viresh Kumar [this message]
2017-07-20 19:49               ` Joel Fernandes
2017-07-21  4:09                 ` Viresh Kumar
2017-07-21  6:02                   ` Joel Fernandes

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=20170720034148.GI352@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=andresoportus@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=joelaf@google.com \
    --cc=juri.lelli@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patrick.bellasi@arm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.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

all inboxes | Powered by JetHome®