From: Quentin Perret <qperret@google.com>
To: Vincent Donnefort <vincent.donnefort@arm.com>
Cc: peterz@infradead.org, mingo@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org, patrick.bellasi@matbug.net,
valentin.schneider@arm.com
Subject: Re: [PATCH] sched/fair: Fix task utilization accountability in cpu_util_next()
Date: Mon, 22 Feb 2021 16:43:39 +0000 [thread overview]
Message-ID: <YDPfO1ixfb+8PNm0@google.com> (raw)
In-Reply-To: <20210222163947.GB225035@e124901.cambridge.arm.com>
On Monday 22 Feb 2021 at 16:39:47 (+0000), Vincent Donnefort wrote:
> On Mon, Feb 22, 2021 at 04:23:42PM +0000, Quentin Perret wrote:
> > On Monday 22 Feb 2021 at 15:58:56 (+0000), Quentin Perret wrote:
> > > But in any case, if we're going to address this, I'm still not sure this
> > > patch will be what we want. As per my first comment we need to keep the
> > > frequency estimation right.
> >
> > Totally untested, but I think in principle you would like something like
> > the snippet below. Would that work?
>
> You preempted my previous email :)
>
> Yeah, that looks like what we want, I'll give a try.
Cool, thanks.
And ofc no strong opinion about the implementation details, this can
most certainly be optimized in some way so have fun :)
Cheers,
Quentin
next prev parent reply other threads:[~2021-02-22 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 9:54 [PATCH] sched/fair: Fix task utilization accountability in cpu_util_next() vincent.donnefort
2021-02-22 10:11 ` Quentin Perret
2021-02-22 11:36 ` Vincent Donnefort
2021-02-22 12:23 ` Quentin Perret
2021-02-22 15:01 ` Vincent Donnefort
2021-02-22 15:58 ` Quentin Perret
2021-02-22 16:23 ` Quentin Perret
2021-02-22 16:39 ` Vincent Donnefort
2021-02-22 16:43 ` Quentin Perret [this message]
2021-02-23 14:47 ` Dietmar Eggemann
2021-02-22 16:31 ` Vincent Donnefort
2021-02-22 16:35 ` Quentin Perret
2021-02-23 14:44 ` Dietmar Eggemann
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=YDPfO1ixfb+8PNm0@google.com \
--to=qperret@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@matbug.net \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.donnefort@arm.com \
--cc=vincent.guittot@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