From: Tejun Heo <tj@kernel.org>
To: Cheng-Yang Chou <yphbchou0911@gmail.com>
Cc: sched-ext@lists.linux.dev, David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chia-Ping Tsai <chia7712@gmail.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-7.2] sched_ext: Refactor scx_root_enable_workfn() enablement task migration
Date: Wed, 22 Apr 2026 07:18:57 -1000 [thread overview]
Message-ID: <aekDAe7GV99mRM7l@slm.duckdns.org> (raw)
In-Reply-To: <20260422094555.Gaec7@cchengyang.duckdns.org>
On Wed, Apr 22, 2026 at 09:53:24AM +0800, Cheng-Yang Chou wrote:
> Regarding the ordering of the task enablement sequence: do you think
> it would be useful to be included in the kdoc?
Who'd be the audience tho? This isn't a level of detail that'd be
interesting to people who want to use SCX. For kernel devs, I don't think a
doc which just restates the code sequence is all that useful when you can
just throw an AI agent at it and get the same and more in no time.
--
tejun
prev parent reply other threads:[~2026-04-22 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 7:41 [PATCH sched_ext/for-7.2] sched_ext: Refactor scx_root_enable_workfn() enablement task migration Cheng-Yang Chou
2026-04-21 17:30 ` Tejun Heo
2026-04-22 1:53 ` Cheng-Yang Chou
2026-04-22 17:18 ` Tejun Heo [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=aekDAe7GV99mRM7l@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=chia7712@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.com \
--cc=yphbchou0911@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.