From: Tejun Heo <tj@kernel.org>
To: Namhyung Kim <namhyung@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ida: fix up bitmap size calculation
Date: Thu, 02 Sep 2010 19:20:36 +0200 [thread overview]
Message-ID: <4C7FDCE4.1080703@kernel.org> (raw)
In-Reply-To: <1283446829-24050-1-git-send-email-namhyung@gmail.com>
Hello,
On 09/02/2010 07:00 PM, Namhyung Kim wrote:
> ida chunk should consist of 128 bytes (= 1024 bits) by definition
> but because of wrong calculation of IDA_BITMAP_LONGS it only contained
> 992 on 32-bit machines, 960 on 64-bit machines. Fix it.
>
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> ---
> include/linux/idr.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/idr.h b/include/linux/idr.h
> index e968db7..13c7296 100644
> --- a/include/linux/idr.h
> +++ b/include/linux/idr.h
> @@ -119,8 +119,8 @@ void idr_init(struct idr *idp);
> * pointer isn't necessary.
> */
> #define IDA_CHUNK_SIZE 128 /* 128 bytes per chunk */
> -#define IDA_BITMAP_LONGS (128 / sizeof(long) - 1)
> -#define IDA_BITMAP_BITS (IDA_BITMAP_LONGS * sizeof(long) * 8)
> +#define IDA_BITMAP_LONGS (IDA_CHUNK_SIZE / sizeof(long))
> +#define IDA_BITMAP_BITS (IDA_CHUNK_SIZE * 8)
The -1 when calculating IDA_BITMAP_LONGS is intentional. Please see
below.
struct ida_bitmap {
long nr_busy;
unsigned long bitmap[IDA_BITMAP_LONGS];
};
With the -1, sizeof(struct ida_bitmap) becomes 128 bytes but if you
remove the -1, it becomes 132 bytes. Because ida_bitmap doesn't use
dedicated slab (doesn't make sense as it's not a very hot data
structure), with 132 bytes, it's gonna be allocated from 256 byte slot
wasting ~50% of memory. Adding a comment there to clarify why -1 is
there would be nice tho.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-09-02 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 17:00 [PATCH] ida: fix up bitmap size calculation Namhyung Kim
2010-09-02 17:20 ` Tejun Heo [this message]
2010-09-02 17:25 ` Namhyung Kim
2010-09-02 18:07 ` Namhyung Kim
2010-09-03 9:14 ` Tejun Heo
2010-09-03 9:26 ` Namhyung Kim
2010-09-03 9:29 ` Tejun Heo
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=4C7FDCE4.1080703@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.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 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.