From: Patrick Bellasi <patrick.bellasi@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Paul Turner <pjt@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>, Todd Kjos <tkjos@android.com>,
Joel Fernandes <joelaf@google.com>,
Steve Muckle <smuckle@google.com>
Subject: Re: [PATCH v5 4/4] sched/fair: update util_est only on util_avg updates
Date: Thu, 8 Mar 2018 10:37:03 +0000 [thread overview]
Message-ID: <20180308103703.GG2211@e110439-lin> (raw)
In-Reply-To: <20180308094830.GK25201@hirez.programming.kicks-ass.net>
On 08-Mar 10:48, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 05:01:53PM +0000, Patrick Bellasi wrote:
> > +#define UTIL_EST_NEED_UPDATE_FLAG 0x1
>
> > @@ -5321,12 +5345,19 @@ static inline void util_est_dequeue(struct cfs_rq *cfs_rq,
> > if (!task_sleep)
> > return;
> >
> > + /*
> > + * Skip update of task's estimated utilization if the PELT signal has
> > + * never been updated (at least once) since last enqueue time.
> > + */
> > + ue = READ_ONCE(p->se.avg.util_est);
> > + if (ue.enqueued & UTIL_EST_NEED_UPDATE_FLAG)
> > + return;
>
> The name and function seem inverted, if the flag is set, we do _NOT_
> update util_est.
My reading was along the line "when the flag is set we need an
update of util_avg to collect a new util_est sample"...
... but I agree that's confusing... and unnecessary long.
> How about something like UTIL_EST_UNCHANGED ? That would give:
I would prefer UTIL_AVG_UNCHANGED, since the flags is reset when we
have a change in util_avg, thus enabling util_est updates.
> /*
> * If the PELT values haven't changed since enqueue time,
> * skip the util_est update.
> */
> if (enqueue & UTIL_EST_UNCHANGED)
> return;
--
#include <best/regards.h>
Patrick Bellasi
prev parent reply other threads:[~2018-03-08 10:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 17:01 [PATCH v5 0/4] Utilization estimation (util_est) for FAIR tasks Patrick Bellasi
2018-02-22 17:01 ` [PATCH v5 1/4] sched/fair: add util_est on top of PELT Patrick Bellasi
2018-03-01 17:42 ` Patrick Bellasi
2018-03-06 18:56 ` Peter Zijlstra
2018-03-07 12:32 ` Patrick Bellasi
2018-03-06 18:58 ` Peter Zijlstra
2018-03-07 9:39 ` Peter Zijlstra
2018-03-07 15:37 ` Patrick Bellasi
2018-03-07 11:31 ` Patrick Bellasi
2018-03-07 12:24 ` Peter Zijlstra
2018-03-07 15:24 ` Patrick Bellasi
2018-03-07 17:35 ` Peter Zijlstra
2018-03-06 19:02 ` Peter Zijlstra
2018-03-07 11:47 ` Patrick Bellasi
2018-03-07 12:26 ` Peter Zijlstra
2018-03-07 15:16 ` Patrick Bellasi
2018-02-22 17:01 ` [PATCH v5 2/4] sched/fair: use util_est in LB and WU paths Patrick Bellasi
2018-02-22 17:01 ` [PATCH v5 3/4] sched/cpufreq_schedutil: use util_est for OPP selection Patrick Bellasi
2018-02-26 4:04 ` Viresh Kumar
2018-03-07 10:12 ` Peter Zijlstra
2018-02-22 17:01 ` [PATCH v5 4/4] sched/fair: update util_est only on util_avg updates Patrick Bellasi
2018-03-01 17:46 ` Patrick Bellasi
2018-03-07 10:38 ` Peter Zijlstra
2018-03-08 9:15 ` Peter Zijlstra
2018-03-08 9:48 ` Peter Zijlstra
2018-03-08 10:37 ` Patrick Bellasi [this message]
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=20180308103703.GG2211@e110439-lin \
--to=patrick.bellasi@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@redhat.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=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=smuckle@google.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