From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Yury Norov <yury.norov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sched_ext: Move built-in idle CPU selection policy to a separate file
Date: Mon, 27 Jan 2025 12:44:27 -1000 [thread overview]
Message-ID: <Z5gMS7V9V-v5ZkRR@slm.duckdns.org> (raw)
In-Reply-To: <20250127222721.627121-1-arighi@nvidia.com>
On Mon, Jan 27, 2025 at 11:27:21PM +0100, Andrea Righi wrote:
> As ext.c is becoming quite large, move the idle CPU selection policy to
> separate files (ext_idle.c / ext_idle.h) for better code readability.
>
> Moreover, group together all the idle CPU selection kfunc's to the same
> btf_kfunc_id_set block.
>
> No functional changes, this is purely code reorganization.
>
> Suggested-by: Yury Norov <yury.norov@gmail.com>
> Signed-off-by: Andrea Righi <arighi@nvidia.com>
Applied to sched_ext/for-6.15.
Thanks.
--
tejun
prev parent reply other threads:[~2025-01-27 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 22:27 Andrea Righi
2025-01-27 22:44 ` 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=Z5gMS7V9V-v5ZkRR@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.com \
--cc=yury.norov@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®