mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: hongyan.xia2@arm.com, mingo@redhat.com, alexs@kernel.org,
	linux-kernel@vger.kernel.org, vschneid@redhat.com,
	bristot@redhat.com, bsegall@google.com, rostedt@goodmis.org,
	dietmar.eggemann@arm.com, peterz@infradead.org,
	juri.lelli@redhat.com, mgorman@suse.de, corbet@lwn.net,
	siyanteng@loongson.cn, qyousef@layalina.io,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] Simplify Util_est
Date: Thu, 30 Nov 2023 12:53:30 +0000	[thread overview]
Message-ID: <f20c8c30-1379-4706-b980-73d2f7e5912a@arm.com> (raw)
In-Reply-To: <20231127143238.1216582-1-vincent.guittot@linaro.org>

Hi Vincent,

On 11/27/23 14:32, Vincent Guittot wrote:
> Following comment in [1], I prepared a patch to remove UTIL_EST_FASTUP.
> This enables us to simplify util_est behavior as proposed in patch 2.
> 
> [1] https://lore.kernel.org/lkml/CAKfTPtCAZWp7tRgTpwJmyEAkyN65acmYrfu9naEUpBZVWNTcQA@mail.gmail.com/
> 
> Vincent Guittot (2):
>    sched/fair: Remove SCHED_FEAT(UTIL_EST_FASTUP, true)
>    sched/fair: Simplify util_est
> 
>   Documentation/scheduler/schedutil.rst |  7 +--
>   include/linux/sched.h                 | 35 ++----------
>   kernel/sched/debug.c                  |  7 +--
>   kernel/sched/fair.c                   | 81 ++++++++++-----------------
>   kernel/sched/features.h               |  1 -
>   kernel/sched/pelt.h                   |  4 +-
>   6 files changed, 43 insertions(+), 92 deletions(-)
> 

I recovered my pixel6 and applied these changes.
No power regression in Jankbench. No performance regression in GB5.
Better score in Chrome running Speedometer +3..5%.

The code looks much more clean, without the 'struct util_est'
(we will have to adjust our trace events to that change but it's worth).

Also, I was a bit surprised that the UTIL_EST_FASTUP wasn't helping
that much comparing to that new 'runnable' signal for the
underestimation corner case...

Reviewed-and-tested-by: Lukasz Luba <lukasz.luba@arm.com>

  parent reply	other threads:[~2023-11-30 12:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 14:32 Vincent Guittot
2023-11-27 14:32 ` [PATCH 1/2] sched/fair: Remove SCHED_FEAT(UTIL_EST_FASTUP, true) Vincent Guittot
2023-11-30 13:42   ` Dietmar Eggemann
2023-11-30 20:30   ` Hongyan Xia
2023-12-01  2:16     ` Tang Yizhou
2023-12-01  7:42       ` Vincent Guittot
2023-12-01  7:41     ` Vincent Guittot
2023-11-27 14:32 ` [PATCH 2/2] sched/fair: Simplify util_est Vincent Guittot
2023-11-30 13:42   ` Dietmar Eggemann
2023-11-30 15:02     ` Vincent Guittot
2023-11-30 20:50   ` Hongyan Xia
2023-11-30 12:53 ` Lukasz Luba [this message]
2023-11-30 14:55   ` [PATCH 0/2] Simplify Util_est Vincent Guittot

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=f20c8c30-1379-4706-b980-73d2f7e5912a@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=alexs@kernel.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=corbet@lwn.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=hongyan.xia2@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=qyousef@layalina.io \
    --cc=rostedt@goodmis.org \
    --cc=siyanteng@loongson.cn \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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®