From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Yury Norov <yury.norov@gmail.com>, Chen Yu <yu.c.chen@intel.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Leonardo Bras <leobras@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Subject: [PATCH 2/2] sched/topology: optimize topology_span_sane()
Date: Wed, 7 Aug 2024 12:05:21 -0700 [thread overview]
Message-ID: <20240807190522.432388-3-yury.norov@gmail.com> (raw)
In-Reply-To: <20240807190522.432388-1-yury.norov@gmail.com>
The function may call cpumask_equal with tl->mask(cpu) == tl->mask(i),
even though cpu != i. In such case, cpumask_equal() would always return
true, and we can proceed to the next iteration immediately.
Comment is provided by Valentin Schneider.
Reviewed-by: Valentin Schneider <vschneid@redhat.com>
Signed-off-by: Yury Norov <yury.norov@gmail.com>
---
kernel/sched/topology.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
index 8af3b48da458..3661d4173d1f 100644
--- a/kernel/sched/topology.c
+++ b/kernel/sched/topology.c
@@ -2370,6 +2370,18 @@ static bool topology_span_sane(struct sched_domain_topology_level *tl,
*/
for_each_cpu_from(i, cpu_map) {
mi = tl->mask(i);
+ /*
+ * Some topology levels (e.g. PKG in default_topology[])
+ * have a sched_domain_mask_f implementation that reuses
+ * the same mask for several CPUs (in PKG's case, one mask
+ * for all CPUs in the same NUMA node).
+ *
+ * For such topology levels, repeating cpumask_equal()
+ * checks is wasteful. Instead, we first check that the
+ * tl->mask(i) pointers aren't the same.
+ */
+ if (mi == mc)
+ continue;
/*
* We should 'and' all those masks with 'cpu_map' to exactly
--
2.43.0
next prev parent reply other threads:[~2024-08-07 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 19:05 [PATCH v2 0/2] " Yury Norov
2024-08-07 19:05 ` [PATCH 1/2] sched/topology: pre-compute topology_span_sane() loop params Yury Norov
2024-08-07 19:05 ` Yury Norov [this message]
2024-08-14 16:35 ` [PATCH v2 0/2] sched/topology: optimize topology_span_sane() Yury Norov
2024-08-28 14:09 ` Yury Norov
2024-08-29 6:11 ` Christophe JAILLET
2024-08-29 13:18 ` Yury Norov
-- strict thread matches above, loose matches on Subject: below --
2024-08-02 17:57 [PATCH " Yury Norov
2024-08-02 17:57 ` [PATCH 2/2] " Yury Norov
2024-08-06 15:50 ` Valentin Schneider
2024-08-06 18:00 ` Yury Norov
2024-08-07 13:53 ` Valentin Schneider
2024-08-07 16:39 ` Yury Norov
[not found] <20240319185148.985729-1-kyle.meyer@hpe.com>
[not found] ` <20240319185148.985729-3-kyle.meyer@hpe.com>
2024-03-20 18:32 ` [PATCH 2/2] sched/topology: Optimize topology_span_sane() Yury Norov
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=20240807190522.432388-3-yury.norov@gmail.com \
--to=yury.norov@gmail.com \
--cc=bsegall@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@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
all inboxes | Powered by JetHome®