From: Peter Zijlstra <peterz@infradead.org>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Valentin Schneider <valentin.schneider@arm.com>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
vincent.guittot@linaro.org, patrick.bellasi@matbug.net,
qperret@google.com, qais.yousef@arm.com,
morten.rasmussen@arm.com
Subject: Re: [PATCH v3 0/5] sched/fair: Task placement biasing using uclamp
Date: Fri, 20 Dec 2019 16:04:18 +0100 [thread overview]
Message-ID: <20191220150418.GK2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <7c9caf20-de5b-3fa2-2663-e712ba3d7829@arm.com>
On Thu, Dec 12, 2019 at 04:06:38PM +0100, Dietmar Eggemann wrote:
> On 11/12/2019 12:38, Valentin Schneider wrote:
> > Hi,
> >
> > While uclamp restrictions currently only impact schedutil's frequency
> > selection, it would make sense to also let them impact CPU selection in
> > asymmetric topologies. This would let us steer specific tasks towards
> > certain CPU capacities regardless of their actual utilization - I give a
> > few examples in patch 4.
> >
> > The first three patches are mainly cleanups, the meat of the thing is
> > in patches 4 and 5.
> >
> > Note that this is in the same spirit as what Patrick had proposed for EAS
> > on Android [1]
> >
> > [1]: https://android.googlesource.com/kernel/common/+/b61876ed122f816660fe49e0de1b7ee4891deaa2%5E%21
>
> Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
> Tested-By: Dietmar Eggemann <dietmar.eggemann@arm.com>
Thanks!
prev parent reply other threads:[~2019-12-20 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 11:38 Valentin Schneider
2019-12-11 11:38 ` [PATCH v3 1/5] sched/uclamp: Remove uclamp_util() Valentin Schneider
2019-12-25 10:39 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2019-12-11 11:38 ` [PATCH v3 2/5] sched/uclamp: Make uclamp util helpers use and return UL values Valentin Schneider
2019-12-25 10:39 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2019-12-11 11:38 ` [PATCH v3 3/5] sched/uclamp: Rename uclamp_util_with() into uclamp_rq_util_with() Valentin Schneider
2019-12-25 10:39 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2019-12-11 11:38 ` [PATCH v3 4/5] sched/fair: Make task_fits_capacity() consider uclamp restrictions Valentin Schneider
2019-12-25 10:39 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2019-12-11 11:38 ` [PATCH v3 5/5] sched/fair: Make EAS wakeup placement " Valentin Schneider
2019-12-25 10:38 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2019-12-12 15:06 ` [PATCH v3 0/5] sched/fair: Task placement biasing using uclamp Dietmar Eggemann
2019-12-20 15:04 ` Peter Zijlstra [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=20191220150418.GK2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@matbug.net \
--cc=qais.yousef@arm.com \
--cc=qperret@google.com \
--cc=valentin.schneider@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
all inboxes | Powered by JetHome®