From: Vincent Donnefort <vdonnefort@google.com>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com,
morten.rasmussen@arm.com, chris.redpath@arm.com,
qperret@google.com, tao.zhou@linux.dev, kernel-team@android.com,
peterz@infradead.org, mingo@redhat.com,
vincent.guittot@linaro.org
Subject: Re: [PATCH v10 0/7] feec() energy margin removal
Date: Tue, 14 Jun 2022 12:47:03 +0100 [thread overview]
Message-ID: <Yqh1N1lhw+hukHD9@google.com> (raw)
In-Reply-To: <6099583c-c986-e1f3-1eee-33b504286757@arm.com>
On Thu, Jun 09, 2022 at 01:53:22PM +0100, Lukasz Luba wrote:
> Hi Vincent,
>
> On 6/7/22 13:32, Vincent Donnefort wrote:
> > Hi,
> >
> > Here's a new version of the patch-set to get rid of the energy margin in
> > feec(). Many thanks to all for the insightful comments I got.
> >
> > find_energy_efficient() (feec()) will migrate a task to save energy only if
> > it saves at least 6% of the total energy consumed by the system. This
> > conservative approach is a problem on a system where a lot of small tasks
> > create a huge load on the overall: very few of them will be allowed to
> > migrate to a smaller CPU, wasting a lot of energy. Instead of trying to
> > determine yet another margin, let's try to remove it.
> >
> > The first elements of this patch-set are various fixes and improvement that
> > stabilizes task_util and ensures energy comparison fairness across all CPUs
> > of the topology. Only once those fixed, we can completely remove the margin
> > and let feec() aggressively place task and save energy.
> >
>
> I've run this patch set on pixel6 (android-mainline) and gathered energy
> values from the meter during the PCmark 3.0.
>
> It looks good, with these patches we have ~10% lower energy usage and
> only ~3% lower score.
>
> There are no other issues, everything works fine. Feel free to add:
>
> Tested-by: Lukasz Luba <lukasz.luba@arm.com>
>
> to the whole patch set.
>
> Regards,
> Lukasz
Thanks a lot Lukasz!
prev parent reply other threads:[~2022-06-14 11:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 12:32 [PATCH v10 0/7] feec() energy margin removal Vincent Donnefort
2022-06-07 12:32 ` [PATCH v10 1/7] sched/fair: Provide u64 read for 32-bits arch helper Vincent Donnefort
2022-06-09 15:23 ` Tao Zhou
2022-06-14 11:45 ` Vincent Donnefort
2022-06-14 14:28 ` Tao Zhou
2022-06-21 8:32 ` Vincent Donnefort
2022-06-07 12:32 ` [PATCH v10 2/7] sched/fair: Decay task PELT values during wakeup migration Vincent Donnefort
2022-06-08 9:53 ` Dietmar Eggemann
2022-06-11 13:56 ` Tao Zhou
2022-06-07 12:32 ` [PATCH v10 3/7] sched, drivers: Remove max param from effective_cpu_util()/sched_cpu_util() Vincent Donnefort
2022-06-07 12:32 ` [PATCH v10 4/7] sched/fair: Rename select_idle_mask to select_rq_mask Vincent Donnefort
2022-06-07 12:32 ` [PATCH v10 5/7] sched/fair: Use the same cpumask per-PD throughout find_energy_efficient_cpu() Vincent Donnefort
2022-06-07 12:32 ` [PATCH v10 6/7] sched/fair: Remove task_util from effective utilization in feec() Vincent Donnefort
2022-06-07 12:32 ` [PATCH v10 7/7] sched/fair: Remove the energy margin " Vincent Donnefort
2022-06-09 12:53 ` [PATCH v10 0/7] feec() energy margin removal Lukasz Luba
2022-06-14 11:47 ` Vincent Donnefort [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=Yqh1N1lhw+hukHD9@google.com \
--to=vdonnefort@google.com \
--cc=chris.redpath@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=tao.zhou@linux.dev \
--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