From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH 0/3] bitmap: optimize small_const path for
Date: Wed, 7 Dec 2022 19:32:40 -0800 [thread overview]
Message-ID: <Y5Fa2BXvO+dpUqf0@yury-laptop> (raw)
In-Reply-To: <Y2Mi7PYO4ihnA+Pb@yury-laptop>
ping again
On Wed, Nov 02, 2022 at 07:09:49PM -0700, Yury Norov wrote:
> Ping?
>
> On Wed, Oct 26, 2022 at 09:38:07PM -0700, Yury Norov wrote:
> > Make all inline bitmap functions __always_inline to ensure that
> > small_const optimization is always possible, and improve on it for
> > find_next_bit() and friends.
> >
> > Yury Norov (3):
> > bitmap: switch from inline to __always_inline
> > bitmap: improve small_const case for find_next() functions
> > bitmap: add tests for find_next_bit()
> >
> > include/asm-generic/bitsperlong.h | 12 +++
> > include/linux/bitmap.h | 46 +++++-----
> > include/linux/cpumask.h | 144 +++++++++++++++---------------
> > include/linux/find.h | 85 ++++++++----------
> > include/linux/nodemask.h | 86 +++++++++---------
> > lib/test_bitmap.c | 23 ++++-
> > 6 files changed, 208 insertions(+), 188 deletions(-)
> >
> > --
> > 2.34.1
prev parent reply other threads:[~2022-12-08 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:38 [PATCH 0/3] bitmap: optimize small_const path for Yury Norov
2022-10-27 4:38 ` [PATCH 1/3] bitmap: switch from inline to __always_inline Yury Norov
2022-10-27 4:38 ` [PATCH 2/3] bitmap: improve small_const case for find_next() functions Yury Norov
2022-10-27 4:38 ` [PATCH 3/3] bitmap: add tests for find_next_bit() Yury Norov
2022-11-03 2:09 ` [PATCH 0/3] bitmap: optimize small_const path for Yury Norov
2022-12-08 3:32 ` Yury Norov [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=Y5Fa2BXvO+dpUqf0@yury-laptop \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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;
as well as URLs for NNTP newsgroup(s).