From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Tim Chen <tim.c.chen@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
"Len Brown" <len.brown@intel.com>, <linux-kernel@vger.kernel.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Arjan Van De Ven <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH v4 1/2] sched: Create architecture specific sched domain distances
Date: Sat, 27 Sep 2025 20:34:25 +0800 [thread overview]
Message-ID: <6a650359-d106-453a-a5a3-24b3750a05d2@intel.com> (raw)
In-Reply-To: <990005f249897c6ef2e7d998c68836eba604f346.1758234869.git.tim.c.chen@linux.intel.com>
On 9/20/2025 1:50 AM, Tim Chen wrote:
> Allow architecture specific sched domain NUMA distances that are
> modified from actual NUMA node distances for the purpose of building
> NUMA sched domains.
>
> Keep actual NUMA distances separately if modified distances
> are used for building sched domains. Such distances
> are still needed as NUMA balancing benefits from finding the
> NUMA nodes that are actually closer to a task numa_group.
>
> Consolidate the recording of unique NUMA distances in an array to
> sched_record_numa_dist() so the function can be reused to record NUMA
> distances when the NUMA distance metric is changed.
>
> No functional change and additional distance array
> allocated if there're no arch specific NUMA distances
> being defined.
>
> Co-developed-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
[snip]
> @@ -1591,10 +1591,12 @@ static void claim_allocations(int cpu, struct sched_domain *sd)
> enum numa_topology_type sched_numa_topology_type;
>
> static int sched_domains_numa_levels;
> +static int sched_numa_node_levels;
I agree that the benefit of maintaining two NUMA distances - one for the
sched_domain and another for the NUMA balancing/page allocation policy - is
to avoid complicating the sched_domain hierarchy while preserving the
advantages of NUMA locality.
Meanwhile, I wonder if we could also add a "orig" prefix to the original
NUMA distance. This way, we can quickly understand its meaning later.
For example,
sched_orig_node_levels
sched_orig_node_distance
> static int sched_domains_curr_level;
>
> int sched_max_numa_distance;
> static int *sched_domains_numa_distance;
> +static int *sched_numa_node_distance;
> static struct cpumask ***sched_domains_numa_masks;
> #endif /* CONFIG_NUMA */
>
> @@ -1808,10 +1810,10 @@ bool find_numa_distance(int distance)
> return true;
>
> rcu_read_lock();
> - distances = rcu_dereference(sched_domains_numa_distance);
> + distances = rcu_dereference(sched_numa_node_distance);
> if (!distances)
> goto unlock;
> - for (i = 0; i < sched_domains_numa_levels; i++) {
> + for (i = 0; i < sched_numa_node_levels; i++) {
> if (distances[i] == distance) {
> found = true;
> break;
> @@ -1887,14 +1889,48 @@ static void init_numa_topology_type(int offline_node)
>
> #define NR_DISTANCE_VALUES (1 << DISTANCE_BITS)
>
> -void sched_init_numa(int offline_node)
> +/*
> + * An architecture could modify its NUMA distance, to change
> + * grouping of NUMA nodes and number of NUMA levels when creating
> + * NUMA level sched domains.
> + *
> + * A NUMA level is created for each unique
> + * arch_sched_node_distance.
> + */
> +static bool __modified_sched_node_dist = true;
> +
> +int __weak arch_sched_node_distance(int from, int to)
> {
> - struct sched_domain_topology_level *tl;
> - unsigned long *distance_map;
> + if (__modified_sched_node_dist)
> + __modified_sched_node_dist = false;
> +
> + return node_distance(from, to);
> +}
> +
> +static bool modified_sched_node_distance(void)
> +{
> + /*
> + * Call arch_sched_node_distance()
> + * to determine if arch_sched_node_distance
> + * has been modified from node_distance()
> + * to arch specific distance.
> + */
> + arch_sched_node_distance(0, 0);
> + return __modified_sched_node_dist;
> +}
> +
If our goal is to figure out whether the arch_sched_node_distance()
has been overridden, how about the following alias?
int __weak arch_sched_node_distance(int from, int to)
{
return __node_distance(from, to);
}
int arch_sched_node_distance_original(int from, int to) __weak
__alias(arch_sched_node_distance);
static bool arch_sched_node_distance_is_overridden(void)
{
return arch_sched_node_distance != arch_sched_node_distance_original;
}
so arch_sched_node_distance_is_overridden() can replace
modified_sched_node_distance()
thanks,
Chenyu
next prev parent reply other threads:[~2025-09-27 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 17:50 [PATCH v4 0/2] Fix NUMA sched domain build errors for GNR and CWF Tim Chen
2025-09-19 17:50 ` [PATCH v4 1/2] sched: Create architecture specific sched domain distances Tim Chen
2025-09-27 12:34 ` Chen, Yu C [this message]
2025-09-29 22:18 ` Tim Chen
2025-09-30 2:28 ` Chen, Yu C
2025-09-30 17:30 ` Tim Chen
2025-10-01 1:10 ` Chen, Yu C
2025-09-19 17:50 ` [PATCH v4 2/2] sched/topology: Fix sched domain build error for GNR, CWF in SNC-3 mode Tim Chen
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=6a650359-d106-453a-a5a3-24b3750a05d2@intel.com \
--to=yu.c.chen@intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tim.c.chen@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vinicius.gomes@intel.com \
--cc=vschneid@redhat.com \
--cc=zhao1.liu@intel.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