From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Yury Norov <yury.norov@gmail.com>
Cc: "Alexander Lobakin" <alobakin@pm.me>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Mao Bibo" <maobibo@loongson.cn>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"WANG Xuerui" <kernel@xen0n.name>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: micro-optimize calculate_cpu_foreign_map()
Date: Tue, 5 Jul 2022 12:40:21 +0200 [thread overview]
Message-ID: <20220705104021.GJ9951@alpha.franken.de> (raw)
In-Reply-To: <Yr5i+OCeb89YMNZw@yury-laptop>
On Thu, Jun 30, 2022 at 07:59:04PM -0700, Yury Norov wrote:
> On Tue, Jun 21, 2022 at 07:47:29AM -0700, Yury Norov wrote:
> > The inner loop in calculate_cpu_foreign_map() walks the whole
> > cpumask to check if we have siblings for a given cpu.
> >
> > We can just break after a 1st match and avoid useless traversing
> > the rest of mask.
> >
> > Loongarch has an identical function, so fix it here as well.
> >
> > Signed-off-by: Yury Norov <yury.norov@gmail.com>
>
> Ping?
as this is touching two different archs, it would have been easier
to send this in two different patches.
Huacai, should I take the patch ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-07-05 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 14:47 [PATCH] mips: micro-optimize calculate_cpu_foreign_map() Yury Norov
2022-07-01 2:59 ` Yury Norov
2022-07-05 10:40 ` Thomas Bogendoerfer [this message]
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=20220705104021.GJ9951@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alobakin@pm.me \
--cc=chenhuacai@kernel.org \
--cc=f4bug@amsat.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maobibo@loongson.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.