From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v5 0/8] bitmap: cleanup bitmap_*_region() implementation
Date: Sat, 14 Oct 2023 19:58:36 -0700 [thread overview]
Message-ID: <ZStVXLWoWwDinETO@yury-ThinkPad> (raw)
In-Reply-To: <ZSA5UlF8e7DRxuqp@yury-ThinkPad>
OK, if no objections, moving this to bitmap-for-next.
On Fri, Oct 06, 2023 at 09:44:04AM -0700, Yury Norov wrote:
> Ping?
>
> On Sun, Sep 24, 2023 at 07:38:09PM -0700, Yury Norov wrote:
> > bitmap_{allocate,find_free,release}_region() functions are implemented
> > on top of _reg_op() machinery. It duplicates existing generic functionality
> > with no benefits. In fact, generic alternatives may work even better
> > because they optimized for small_const_nbits() case and overall very well
> > optimized for performance and code generation.
> >
> > This series drops _reg_op() entirely.
> >
> > v2: https://lore.kernel.org/lkml/20230811005732.107718-2-yury.norov@gmail.com/T/
> > v3: https://lore.kernel.org/lkml/20230815233628.45016-2-yury.norov@gmail.com/T/
> > v4: https://lore.kernel.org/lkml/20230829023911.64335-1-yury.norov@gmail.com/T/
> > v5: - fix bitmap_release_region() implementation;
> > - address nits for commits comments.
> >
> > Yury Norov (8):
> > bitmap: align __reg_op() wrappers with modern coding style
> > bitmap: add test for bitmap_*_region() functions
> > bitmap: fix opencoded bitmap_allocate_region()
> > bitmap: replace _reg_op(REG_OP_ALLOC) with bitmap_set()
> > bitmap: replace _reg_op(REG_OP_RELEASE) with bitmap_clear()
> > bitmap: replace _reg_op(REG_OP_ISFREE) with find_next_bit()
> > bitmap: drop _reg_op() function
> > bitmap: move bitmap_*_region() functions to bitmap.h
> >
> > include/linux/bitmap.h | 63 ++++++++++++++++++-
> > lib/bitmap.c | 140 -----------------------------------------
> > lib/test_bitmap.c | 24 +++++++
> > 3 files changed, 84 insertions(+), 143 deletions(-)
> >
> > --
> > 2.39.2
prev parent reply other threads:[~2023-10-15 2:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 2:38 [PATCH v5 0/8] bitmap: cleanup bitmap_*_region() implementation Yury Norov
2023-09-25 2:38 ` [PATCH v5 1/8] bitmap: align __reg_op() wrappers with modern coding style Yury Norov
2023-09-25 2:38 ` [PATCH v5 2/8] bitmap: add test for bitmap_*_region() functions Yury Norov
2023-09-25 2:38 ` [PATCH v5 3/8] bitmap: fix opencoded bitmap_allocate_region() Yury Norov
2023-09-25 2:38 ` [PATCH v5 4/8] bitmap: replace _reg_op(REG_OP_ALLOC) with bitmap_set() Yury Norov
2023-09-25 2:38 ` [PATCH v5 5/8] bitmap: replace _reg_op(REG_OP_RELEASE) with bitmap_clear() Yury Norov
2023-09-25 2:38 ` [PATCH v5 6/8] bitmap: replace _reg_op(REG_OP_ISFREE) with find_next_bit() Yury Norov
2023-09-25 2:38 ` [PATCH v5 7/8] bitmap: drop _reg_op() function Yury Norov
2023-09-25 2:38 ` [PATCH v5 8/8] bitmap: move bitmap_*_region() functions to bitmap.h Yury Norov
2023-10-06 16:44 ` [PATCH v5 0/8] bitmap: cleanup bitmap_*_region() implementation Yury Norov
2023-10-15 2:58 ` 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=ZStVXLWoWwDinETO@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--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