From: Steven Rostedt <rostedt@goodmis.org>
To: Zihuan Zhang <zhangzihuan@kylinos.cn>
Cc: Christian Loehle <christian.loehle@arm.com>,
xuewen.yan@unisoc.com, vincent.guittot@linaro.org,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
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: Re: [PATCH v1] sched/uclamp: Exclude kernel threads from uclamp logic
Date: Thu, 3 Jul 2025 10:51:47 -0400 [thread overview]
Message-ID: <20250703105147.13e10a77@batman.local.home> (raw)
In-Reply-To: <6414cb05-11d3-4b2a-ae97-7bb0ca0ea898@kylinos.cn>
On Thu, 3 Jul 2025 18:07:20 +0800
Zihuan Zhang <zhangzihuan@kylinos.cn> wrote:
> As Xuewen mentioned, some kernel threads may intentionally set
> scheduling attributes for performance. So instead of unconditionally
> excluding all kernel threads, I’m now considering a more conservative
> approach:
> skip only those kthreads that haven’t explicitly set any clamp values.
The above comment bothers me. What kernel threads set scheduling attributes?
From my experience working on real-time, no kernel thread gets
scheduling tweaking correct.
-- Steve
next prev parent reply other threads:[~2025-07-03 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 9:14 Zihuan Zhang
2025-07-03 9:22 ` Christian Loehle
2025-07-03 10:07 ` Zihuan Zhang
2025-07-03 10:17 ` Christian Loehle
2025-07-10 0:47 ` Zihuan Zhang
2025-07-10 3:41 ` K Prateek Nayak
2025-07-15 6:05 ` Zihuan Zhang
2025-07-10 8:41 ` Christian Loehle
2025-07-15 5:54 ` Zihuan Zhang
2025-07-03 14:51 ` Steven Rostedt [this message]
2025-07-10 0:55 ` Zihuan Zhang
2025-07-10 14:03 ` Steven Rostedt
2025-07-15 5:59 ` Zihuan Zhang
2025-07-03 9:42 ` Xuewen Yan
2025-07-03 10:14 ` Zihuan Zhang
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=20250703105147.13e10a77@batman.local.home \
--to=rostedt@goodmis.org \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=di.shen@unisoc.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=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.com \
--cc=zhangzihuan@kylinos.cn \
/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®