The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 sched_ext/for-6.13] sched_ext: Do not enable LLC/NUMA optimizations when domains overlap
Date: Tue, 5 Nov 2024 13:32:05 -1000	[thread overview]
Message-ID: <Zyqq9fnsOg56aO7S@slm.duckdns.org> (raw)
In-Reply-To: <20241031073401.13034-1-arighi@nvidia.com>

Hello, Andrea.

Sorry about the delay.

On Thu, Oct 31, 2024 at 08:34:01AM +0100, Andrea Righi wrote:
> @@ -3154,16 +3154,29 @@ static void update_selcpu_topology(void)
>  	rcu_read_lock();
>  	sd = rcu_dereference(per_cpu(sd_llc, cpu));
>  	if (sd) {
> -		cpus = sched_domain_span(sd);
> -		if (cpumask_weight(cpus) < num_possible_cpus())
> +		llc_cpus = sched_domain_span(sd);
> +		if (cpumask_weight(llc_cpus) < num_possible_cpus())

Not from this patch but should the weight be compared against
num_online_cpus()? Sched domains don't include offline CPUs, right?

...
> +	/*
> +	 * If the NUMA domain perfectly overlaps with the LLC domain, enable
> +	 * LLC optimization only, as checking for an idle CPU in the same
> +	 * domain twice is redundant.
> +	 */
> +	if (enable_numa && enable_llc && cpumask_equal(numa_cpus, llc_cpus))
> +		enable_numa = false;
> +	/*
> +	 * If all the online CPUs are in the same LLC domain, there is no
> +	 * reason to enable LLC optimization.
> +	 */
> +	if (enable_llc && cpumask_equal(llc_cpus, cpu_online_mask))
> +		enable_llc = false;

The second test looks like it should always be correct. I'm not sure the
first one is. It probably is good enough but would at least be worthwhile to
explain why that is?

Thanks.

-- 
tejun

  reply	other threads:[~2024-11-05 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31  7:34 [PATCH sched_ext/for-6.13] sched_ext: Do not enable LLC/NUMA optimizations when domains overlap Andrea Righi
2024-11-05 23:32 ` Tejun Heo [this message]
2024-11-06  0:29   ` Andrea Righi
2024-11-06  0:33     ` Tejun Heo
2024-11-06  1:08       ` Andrea Righi
2024-11-06  1:15         ` Tejun Heo
2024-11-06  1:25           ` Tejun Heo

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=Zyqq9fnsOg56aO7S@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