From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: 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: Re: [PATCH v2 0/2] sched/topology: optimize topology_span_sane()
Date: Wed, 28 Aug 2024 07:09:30 -0700 [thread overview]
Message-ID: <Zs8vmpwY2Dt9s0Ei@yury-ThinkPad> (raw)
In-Reply-To: <ZrzcozFadC5xQdUq@yury-ThinkPad>
Ping again?
On Wed, Aug 14, 2024 at 09:35:04AM -0700, Yury Norov wrote:
> Ping?
>
> On Wed, Aug 07, 2024 at 12:05:19PM -0700, Yury Norov wrote:
> > The function may call cpumask_equal with tl->mask(cpu) == tl->mask(i),
> > even when cpu != i. In such case, cpumask_equal() would always return
> > true, and we can proceed to the next iteration immediately.
> >
> > Valentin Schneider shares on it:
> >
> > PKG can potentially hit that condition, and so can any
> > sched_domain_mask_f that relies on the node masks...
> >
> > I'm thinking ideally we should have checks in place to
> > ensure all node_to_cpumask_map[] masks are disjoint,
> > then we could entirely skip the levels that use these
> > masks in topology_span_sane(), but there's unfortunately
> > no nice way to flag them... Also there would be cases
> > where there's no real difference between PKG and NODE
> > other than NODE is still based on a per-cpu cpumask and
> > PKG isn't, so I don't see a nicer way to go about this.
> >
> > v1: https://lore.kernel.org/lkml/ZrJk00cmVaUIAr4G@yury-ThinkPad/T/
> > v2:
> > - defer initialization of 'mc' in patch #1 @Chen Yu;
> > - more comments from Valentin Schneider.
> >
> >
> > Yury Norov (2):
> > sched/topology: pre-compute topology_span_sane() loop params
> > sched/topology: optimize topology_span_sane()
> >
> > kernel/sched/topology.c | 20 ++++++++++++++++++--
> > 1 file changed, 18 insertions(+), 2 deletions(-)
> >
> > --
> > 2.43.0
next prev parent reply other threads:[~2024-08-28 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 19:05 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 ` [PATCH 2/2] sched/topology: optimize topology_span_sane() Yury Norov
2024-08-14 16:35 ` [PATCH v2 0/2] " Yury Norov
2024-08-28 14:09 ` Yury Norov [this message]
2024-08-29 6:11 ` Christophe JAILLET
2024-08-29 13:18 ` Yury Norov
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 21:33 [PATCH v2 0/2] sched/topology: Optimize topology_span_sane() Kyle Meyer
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=Zs8vmpwY2Dt9s0Ei@yury-ThinkPad \
--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®