From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched_ext: Introduce NUMA awareness to the default idle selection policy
Date: Fri, 25 Oct 2024 10:02:31 -1000 [thread overview]
Message-ID: <Zxv5V5mwDAlGzpBb@slm.duckdns.org> (raw)
In-Reply-To: <20241025162535.88059-1-arighi@nvidia.com>
Hello,
On Fri, Oct 25, 2024 at 06:25:35PM +0200, Andrea Righi wrote:
...
> +static DEFINE_STATIC_KEY_FALSE(scx_topology_llc);
> +static DEFINE_STATIC_KEY_FALSE(scx_topology_numa);
Maybe name them sth like scx_selcpu_topo_llc given that this is only used by
selcpu?
> +static void init_topology(void)
Ditto with naming.
> {
> - struct sched_domain *sd = rcu_dereference(per_cpu(sd_llc, cpu));
> - const struct cpumask *llc_cpus = sd ? sched_domain_span(sd) : NULL;
> + const struct cpumask *cpus;
> + int nid;
> + s32 cpu;
> +
> + /*
> + * Detect if the system has multiple NUMA nodes distributed across the
> + * available CPUs and, in that case, enable NUMA-aware scheduling in
> + * the default CPU idle selection policy.
> + */
> + for_each_node(nid) {
> + cpus = cpumask_of_node(nid);
> + if (cpumask_weight(cpus) < nr_cpu_ids) {
Comparing number of cpus with nr_cpu_ids doesn't work. The above condition
can trigger on single node machines with some CPUs offlines or unavailable
for example. I think num_node_state(N_CPU) should work or if you want to
keep with sched_domains, maybe highest_flag_domain(some_cpu,
SD_NUMA)->groups->weight would work?
...
> + for_each_possible_cpu(cpu) {
> + struct sched_domain *sd = rcu_dereference(per_cpu(sd_llc, cpu));
> +
> + if (!sd)
> + continue;
> + cpus = sched_domain_span(sd);
> + if (cpumask_weight(cpus) < nr_cpu_ids) {
Ditto.
...
> + /*
> + * Determine the scheduling domain only if the task is allowed to run
> + * on all CPUs.
> + *
> + * This is done primarily for efficiency, as it avoids the overhead of
> + * updating a cpumask every time we need to select an idle CPU (which
> + * can be costly in large SMP systems), but it also aligns logically:
> + * if a task's scheduling domain is restricted by user-space (through
> + * CPU affinity), the task will simply use the flat scheduling domain
> + * defined by user-space.
> + */
> + if (p->nr_cpus_allowed == nr_cpu_ids) {
Should compare against nr_possible_cpus.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-10-25 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 16:25 Andrea Righi
2024-10-25 20:02 ` Tejun Heo [this message]
2024-10-27 8:08 ` Andrea Righi
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=Zxv5V5mwDAlGzpBb@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.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®