From: Andrew Morton <akpm@linux-foundation.org>
To: Chanho Min <chanho.min@lge.com>
Cc: Nadia Yvette Chambers <nyc@holomorphy.com>,
Jiri Kosina <jkosina@suse.cz>, Guennadi Liakhovetski <lg@denx.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bitmap: speedup in bitmap_find_free_region when order is 0
Date: Mon, 8 Apr 2013 14:30:37 -0700 [thread overview]
Message-ID: <20130408143037.5fe18306172315fc040329de@linux-foundation.org> (raw)
In-Reply-To: <1365387828-24326-1-git-send-email-chanho.min@lge.com>
On Mon, 8 Apr 2013 11:23:48 +0900 Chanho Min <chanho.min@lge.com> wrote:
> If bitmap_find_free_region() is called with order=0, We can reduce
> for-loops to find 1 free bit. First, It scans bitmap array by the
> increment of long type, then find 1 free bit within 1 long type value.
That seems sensible. I assume-without-checking that single-bit is a
common case?
> In 32 bits system and 1024 bits size, in the worst case, We need 1024
> for-loops to find 1 free bit. But, If This is applied, it takes
> 64 for-loops. Instead, if free bit is in the first index of the bitmaps,
> It will be needed additional 1 for-loop. But from second index, It
> will be speed up significantly.
>
> --- a/lib/bitmap.c
> +++ b/lib/bitmap.c
> @@ -1099,6 +1099,37 @@ done:
> }
>
> /**
> + * bitmap_find_free_one - find a mem region
> + * @bitmap: array of unsigned longs corresponding to the bitmap
> + * @bits: number of bits in the bitmap
> + *
> + * Find one of free (zero) bits in a @bitmap of @bits bits and
> + * allocate them (set them to one).
> + *
> + * Return the bit offset in bitmap of the allocated region,
> + * or -errno on failure.
> + */
> +static int __bitmap_find_free_one(unsigned long *bitmap, int bits)
> +{
> + int pos, i;
> + unsigned long mask = (unsigned long)(~((unsigned long) 0));
That seems unnecessarily complicated. "unsigned long mask = -1;" works :)
> + int nlongs_reg = BITS_TO_LONGS(bits);
> +
> + for (i = 0 ; i < nlongs_reg ; i++) {
> + if ((bitmap[i] & mask) != mask) {
But here we could just do "if (bitmap[i] != -1)". Or ~0UL.
> + for (pos = 0 ; pos < BITS_PER_LONG ; pos++) {
> + if (!__reg_op(&bitmap[i], pos, 0,
> + REG_OP_ISFREE))
> + continue;
> + __reg_op(&bitmap[i], pos, 0, REG_OP_ALLOC);
> + return pos;
> + }
> + }
> + }
> + return -ENOMEM;
> +}
afacit the code is buggy - if `bits' is not an exact multiple of
BITS_PER_LONG, this search will wander off the end of the specified
region?
> +/**
> * bitmap_find_free_region - find a contiguous aligned mem region
> * @bitmap: array of unsigned longs corresponding to the bitmap
> * @bits: number of bits in the bitmap
> @@ -1116,6 +1147,9 @@ int bitmap_find_free_region(unsigned long *bitmap, int bits, int order)
> {
> int pos, end; /* scans bitmap by regions of size order */
>
> + if (order == 0)
> + return __bitmap_find_free_one(bitmap, bits);
> +
> for (pos = 0 ; (end = pos + (1 << order)) <= bits; pos = end) {
> if (!__reg_op(bitmap, pos, order, REG_OP_ISFREE))
> continue;
next prev parent reply other threads:[~2013-04-08 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 2:23 Chanho Min
2013-04-08 21:30 ` Andrew Morton [this message]
2013-04-08 21:35 ` Joe Perches
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=20130408143037.5fe18306172315fc040329de@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chanho.min@lge.com \
--cc=jkosina@suse.cz \
--cc=lg@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nyc@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®