From: Tejun Heo <tj@kernel.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Namhyung Kim <namhyung@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ida: document IDA_BITMAP_LONGS calculation
Date: Thu, 23 Sep 2010 13:28:28 +0200 [thread overview]
Message-ID: <4C9B39DC.8050409@kernel.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1009231325370.26813@pobox.suse.cz>
On 09/23/2010 01:25 PM, Jiri Kosina wrote:
> On Fri, 3 Sep 2010, Namhyung Kim wrote:
>
>> IDA_BITMAP_LONGS value is calculated take into account struct ida_bitmap
>> not to waste memory space. Comment it.
>>
>> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
>> Acked-by: Tejun Heo <tj@kernel.org>
>> ---
>> include/linux/idr.h | 5 ++++-
>> 1 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/include/linux/idr.h b/include/linux/idr.h
>> index e968db7..3f4b718 100644
>> --- a/include/linux/idr.h
>> +++ b/include/linux/idr.h
>> @@ -117,10 +117,13 @@ void idr_init(struct idr *idp);
>> /*
>> * IDA - IDR based id allocator, use when translation from id to
>> * pointer isn't necessary.
>> + *
>> + * IDA_BITMAP_LONGS is calculated to be one less to accommodate
>> + * ida_bitmap->nr_busy so that the whole struct fits in 128 bytes.
>> */
>> #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_BITS (IDA_BITMAP_LONGS * sizeof(long) * 8)
>>
>> struct ida_bitmap {
>> long nr_busy;
>
> Tejun, any word on this patch? Doesn't seem to be present in linux-next.
Ooh, I was hoping this one could go through the trivial tree. It
would be great if you can pick up the patch.
Thank you.
--
tejun
next prev parent reply other threads:[~2010-09-23 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 9:38 [PATCH] ida: document IDA_BITMAP_LONGS calculation Namhyung Kim
2010-09-23 11:25 ` Jiri Kosina
2010-09-23 11:28 ` Tejun Heo [this message]
2010-09-23 11:52 ` Jiri Kosina
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=4C9B39DC.8050409@kernel.org \
--to=tj@kernel.org \
--cc=jkosina@suse.cz \
--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.