From: Andrea Righi <arighi@nvidia.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] sched_ext: Introduce per-NUMA idle cpumasks
Date: Tue, 3 Dec 2024 08:38:41 +0100 [thread overview]
Message-ID: <Z061gVVaFwRwd-U0@gpd3> (raw)
In-Reply-To: <Z0suMHchW-KyIGyy@gpd3>
On Sat, Nov 30, 2024 at 04:24:36PM +0100, Andrea Righi wrote:
> On Fri, Nov 29, 2024 at 11:38:53AM -0800, Yury Norov wrote:
> ...
> > > static s32 scx_pick_idle_cpu(const struct cpumask *cpus_allowed, u64 flags)
> > > {
> > > - int cpu;
> > > + int start = cpu_to_node(smp_processor_id());
> > > + int node, cpu;
> > >
> > > retry:
> > > if (sched_smt_active()) {
> > > - cpu = cpumask_any_and_distribute(idle_masks.smt, cpus_allowed);
> > > - if (cpu < nr_cpu_ids)
> > > - goto found;
> > > + for_each_node_state_wrap(node, N_ONLINE, start) {
> > > + if (!cpumask_intersects(idle_masks[node]->smt, cpus_allowed))
> > > + continue;
> > > + cpu = cpumask_any_and_distribute(idle_masks[node]->smt, cpus_allowed);
> > > + if (cpu < nr_cpu_ids)
> > > + goto found;
> > > + }
> >
> > Here the same consideration is applicable as for v1:
> > if idle_masks[node]->smt and cpus_allowed are disjoint, the
> > cpumask_any_and_distribute() will return >= nr_cpu_ids, and we'll go to
> > the next iteration. No need to call cpumask_intersects().
>
> For some reason, removing cpumask_intersects() here seems to introduce a
> slight performance drop.
>
> My initial assumption was that the performance drop occurs because
> cpus_allowed often doesn't intersect with idle_masks[node]->smt (since
> cpus_allowed usually doesn't span multiple NUMA nodes), so running
> cpumask_any_and_distribute() on N cpumasks (worst case) is slower than
> first checking for an intersection.
>
> However, I will rerun the test to ensure that the regression is
> consistent and not just a measurement error.
I did more testing and the slight performance drop is not consistent,
therefore, I believe we can attribute it to measurement errors.
I'll send a v3 that removes cpumask_intersects() and includes some minor
code refactoring.
-Andrea
next prev parent reply other threads:[~2024-12-03 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 17:54 [PATCHSET v2 sched_ext/for-6.13] sched_ext: split global idle cpumask into per-NUMA cpumasks Andrea Righi
2024-11-29 17:54 ` [PATCH 1/2] nodemask: Introduce for_each_node_mask_wrap/for_each_node_state_wrap() Andrea Righi
2024-11-29 19:27 ` Yury Norov
2024-11-30 15:13 ` Andrea Righi
2024-11-29 17:54 ` [PATCH 2/2] sched_ext: Introduce per-NUMA idle cpumasks Andrea Righi
2024-11-29 19:38 ` Yury Norov
2024-11-30 15:24 ` Andrea Righi
2024-12-03 7:38 ` Andrea Righi [this message]
2024-12-03 14:16 ` Andrea Righi
-- strict thread matches above, loose matches on Subject: below --
2024-11-26 9:56 [PATCHSET sched_ext/for-6.13] sched_ext: split global idle cpumask into per-NUMA cpumasks Andrea Righi
2024-11-26 9:56 ` [PATCH 2/2] sched_ext: Introduce per-NUMA idle cpumasks Andrea Righi
2024-11-27 2:35 ` Yury Norov
2024-11-27 7:41 ` 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=Z061gVVaFwRwd-U0@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