From: Yury Norov <yury.norov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH 0/4] lib/group_cpus: rework grp_spread_init_one() and make it O(1)
Date: Mon, 4 Dec 2023 14:01:07 -0800 [thread overview]
Message-ID: <ZW5MI3rKQueLM0Bz@yury-ThinkPad> (raw)
In-Reply-To: <20231101225820.51342-1-yury.norov@gmail.com>
Ping?
On Wed, Nov 01, 2023 at 03:58:16PM -0700, Yury Norov wrote:
> grp_spread_init_one() implementation is sub-optimal now because it
> traverses bitmaps from the beginning, instead of picking from the
> previous iteration.
>
> Fix it and use find_bit API where appropriate.
>
> Yury Norov (4):
> cpumask: introduce for_each_cpu_and_from()
> lib/group_cpus: relax atomicity requirement in grp_spread_init_one()
> lib/group_cpus: optimize inner loop in grp_spread_init_one()
> lib/group_cpus: optimize outer loop in grp_spread_init_one()
>
> include/linux/cpumask.h | 11 +++++++++++
> include/linux/find.h | 3 +++
> lib/group_cpus.c | 29 ++++++++++++-----------------
> 3 files changed, 26 insertions(+), 17 deletions(-)
>
> --
> 2.39.2
next prev parent reply other threads:[~2023-12-04 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 22:58 [PATCH 0/4] lib/group_cpus: rework grp_spread_init_one() and make it O(1) Yury Norov
2023-11-01 22:58 ` [PATCH 1/4] cpumask: introduce for_each_cpu_and_from() Yury Norov
2023-11-01 22:58 ` [PATCH 2/4] lib/group_cpus: relax atomicity requirement in grp_spread_init_one() Yury Norov
2023-11-01 22:58 ` [PATCH 3/4] lib/group_cpus: optimize inner loop " Yury Norov
2023-11-01 22:58 ` [PATCH 4/4] lib/group_cpus: optimize outer " Yury Norov
2023-12-04 22:01 ` Yury Norov [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 22:34 [PATCH 0/4] lib/group_cpus: rework grp_spread_init_one() and make it O(1) 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=ZW5MI3rKQueLM0Bz@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=tglx@linutronix.de \
/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.