From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>
Cc: Yury Norov <yury.norov@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET v6 sched_ext/for-6.14] sched_ext: split global idle cpumask into per-NUMA cpumasks
Date: Tue, 10 Dec 2024 00:23:03 +0100 [thread overview]
Message-ID: <Z1d714H-YSMrd0Dq@gpd3> (raw)
In-Reply-To: <20241209230242.775225-1-arighi@nvidia.com>
On Mon, Dec 09, 2024 at 11:56:24PM +0100, Andrea Righi wrote:
...
> ChangeLog v5 -> v6:
> - refactor patch set to introduce SCX_OPS_NODE_BUILTIN_IDLE before
> the per-node cpumasks
> - move idle CPU selection policy to a separate file (ext_idle.c)
> (no functional change, just some code shuffling)
It seems that I totally missed some comments from Yury, I'll address
them in a new version. Apologize for the noise.
-Andrea
prev parent reply other threads:[~2024-12-09 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 22:56 [PATCHSET v6 sched_ext/for-6.14] sched_ext: split global idle cpumask into per-NUMA cpumasks Andrea Righi
2024-12-09 22:56 ` [PATCH 1/6] sched_ext: Introduce SCX_OPS_NODE_BUILTIN_IDLE Andrea Righi
2024-12-09 22:56 ` [PATCH 2/6] sched_ext: Introduce per-node idle cpumasks Andrea Righi
2024-12-09 22:56 ` [PATCH 3/6] sched_ext: Get rid of the scx_selcpu_topo_numa logic Andrea Righi
2024-12-09 22:56 ` [PATCH 4/6] sched_ext: Use SCX_OPS_NODE_BUILTIN_IDLE Andrea Righi
2024-12-09 22:56 ` [PATCH 5/6] sched_ext: Introduce NUMA aware idle cpu kfunc helpers Andrea Righi
2024-12-09 22:56 ` [PATCH 6/6] sched_ext: Move built-in idle CPU selection policy to a separate file Andrea Righi
2024-12-09 23:23 ` Andrea Righi [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=Z1d714H-YSMrd0Dq@gpd3 \
--to=arighi@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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