From: Yury Norov <yury.norov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH] bitmap: optimize bitmap_remap()
Date: Thu, 17 Aug 2023 07:21:59 -0700 [thread overview]
Message-ID: <ZN4tB7jkQrX/TKnh@yury-ThinkPad> (raw)
In-Reply-To: <ZN3qlCd+TcYiZg+s@smile.fi.intel.com>
On Thu, Aug 17, 2023 at 12:38:28PM +0300, Andy Shevchenko wrote:
> On Thu, Aug 17, 2023 at 12:37:05PM +0300, Andy Shevchenko wrote:
> > On Tue, Aug 15, 2023 at 04:59:34PM -0700, Yury Norov wrote:
>
> ...
>
> > > int n = bitmap_pos_to_ord(old, oldbit, nbits);
> > >
> > > + bit = (n < 0) ? oldbit : /* identity map */
> >
> > Can't you also optimize this case?
> >
> > Something like
> >
> > bitmap_xor(tmp, old, new) // maybe even better approach, dunno
>
> > bitmap_empty(tmp) // can be replaced by find first bit
>
> Or reuse bitmap_weight()...
That way it wouldn't work, but I think something like this would:
if (dst == src) /* following doesn't handle inplace remaps */
return;
w = bitmap_weight(new, nbits);
if (w == 0) {
bitmap_copy(dst, src, nbits);
return;
}
/* Identity part */
bitmap_andnot(dst, src, old, nbits);
for_each_and_bit(oldbit, src, old, nbits) {
int n = bitmap_weight(old, oldbit);
__set_bit(find_nth_bit(new, nbits, n % w), dst);
}
And it needs bitmap_weight_from() and find_nth_bit_from() to avoid
Schlemiel the Painter's problem.
You're right. This has a room for more optimizations. Thanks for
discussion. Need to give it a run.
Thanks,
Yury
next prev parent reply other threads:[~2023-08-17 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 23:59 [PATCH] bitmap: optimize bitmap_remap() Yury Norov
2023-08-17 9:37 ` Andy Shevchenko
2023-08-17 9:38 ` Andy Shevchenko
2023-08-17 14:21 ` Yury Norov [this message]
2023-08-17 15:37 ` Andy Shevchenko
2023-08-19 2:03 ` Yury Norov
2023-08-21 7:48 ` Rasmus Villemoes
2023-08-21 8:56 ` Andy Shevchenko
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=ZN4tB7jkQrX/TKnh@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;
as well as URLs for NNTP newsgroup(s).