From: Xuewen Yan <xuewen.yan@unisoc.com>
To: <vincent.guittot@linaro.org>, <dietmar.eggemann@arm.com>,
<mingo@redhat.com>, <peterz@infradead.org>,
<juri.lelli@redhat.com>
Cc: <rostedt@goodmis.org>, <bsegall@google.com>, <mgorman@suse.de>,
<vschneid@redhat.com>, <hongyan.xia2@arm.com>,
<linux-kernel@vger.kernel.org>, <ke.wang@unisoc.com>,
<di.shen@unisoc.com>, <xuewen.yan94@gmail.com>,
<kprateek.nayak@amd.com>, <kuyo.chang@mediatek.com>,
<juju.sung@mediatek.com>, <qyousef@layalina.io>
Subject: [PATCH V3 0/2] sched: Align uclamp and util_est
Date: Thu, 17 Apr 2025 12:34:55 +0800 [thread overview]
Message-ID: <20250417043457.10632-1-xuewen.yan@unisoc.com> (raw)
Now, both uclamp and util_est have been adapted for DELAYED_DEQUEUE,
and the double enqueue/dequeue issue no longer exists.
However, there is still room for optimization in both uclamp and util_est.
Previous discussions as following:
https://lore.kernel.org/all/CAB8ipk8pEvOtCm-d0o1rsekwxPWUHk9iBGtt9TLTWW-iWTQKiA@mail.gmail.com/
https://lore.kernel.org/all/84441660bef0a5e67fd09dc3787178d0276dad31.1740664400.git.hongyan.xia2@arm.com/T/#u
https://lore.kernel.org/all/CAB8ipk9LpbiUDnbcV6+59+Sa=Ai7tFzO===mpLD3obNdV4=J-A@mail.gmail.com/T/#u
https://lore.kernel.org/all/aa8baf67-a8ec-4ad8-a6a8-afdcd7036771@arm.com/
https://lore.kernel.org/all/20250325014733.18405-1-xuewen.yan@unisoc.com/
patch[1]: Simply the condition for util_est_dequeue/enqueue;
patch[2] aligns uclamp and util_est and call before freq update to improve
the performance and power.
Xuewen Yan (2):
sched/util_est: Simply the condition for util_est_dequeue/enqueue
sched/uclamp: Align uclamp and util_est and call before freq update
kernel/sched/core.c | 17 ++++++++++-------
kernel/sched/fair.c | 4 ++--
2 files changed, 12 insertions(+), 9 deletions(-)
---
v3:
- split previous patch in 2 patches.
v2:
- simply the util-est's en/dequeue check;
---
--
2.25.1
next reply other threads:[~2025-04-17 4:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 4:34 Xuewen Yan [this message]
2025-04-17 4:34 ` [PATCH V3 1/2] sched/util_est: Simply the condition for util_est_dequeue/enqueue Xuewen Yan
2025-04-18 15:00 ` Vincent Guittot
2025-04-22 15:27 ` Dietmar Eggemann
2025-05-21 12:06 ` [tip: sched/core] sched/util_est: Simplify condition for util_est_{en,de}queue() tip-bot2 for Xuewen Yan
2025-04-17 4:34 ` [PATCH V3 2/2] sched/uclamp: Align uclamp and util_est and call before freq update Xuewen Yan
2025-04-18 15:00 ` Vincent Guittot
2025-05-21 12:06 ` [tip: sched/core] " tip-bot2 for Xuewen Yan
2025-04-22 15:27 ` [PATCH V3 0/2] sched: Align uclamp and util_est Dietmar Eggemann
2025-05-20 5:59 ` Xuewen Yan
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=20250417043457.10632-1-xuewen.yan@unisoc.com \
--to=xuewen.yan@unisoc.com \
--cc=bsegall@google.com \
--cc=di.shen@unisoc.com \
--cc=dietmar.eggemann@arm.com \
--cc=hongyan.xia2@arm.com \
--cc=juju.sung@mediatek.com \
--cc=juri.lelli@redhat.com \
--cc=ke.wang@unisoc.com \
--cc=kprateek.nayak@amd.com \
--cc=kuyo.chang@mediatek.com \
--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=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=xuewen.yan94@gmail.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®