From: Paul Mundt <lethal@linux-sh.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
an Molton <spyro@f2s.com>,
tony@atomide.com, jamey.hicks@hp.com, joshua@joshuawise.com,
david-b@pacbell.net, Russell King <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] bitmap: Support for pages > BITS_PER_LONG.
Date: Fri, 20 Jan 2006 09:28:51 +0200 [thread overview]
Message-ID: <20060120072851.GA3918@linux-sh.org> (raw)
In-Reply-To: <1137727710.3571.51.camel@mulgrave>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
On Thu, Jan 19, 2006 at 09:28:30PM -0600, James Bottomley wrote:
> On Wed, 2006-01-18 at 19:11 -0800, Paul Jackson wrote:
> > Could you look Mundt's patch, and see if it looks ok?
>
> Not being on lkml, this was harder than it sounds, but I eventually
> found the actual patch on marc. However, no, it doesn't look right.
>
> This:
>
> > + /* find space in the bitmap */
> > + for (j = 0; j < span; j++)
> > + if ((bitmap[index + j] & (mask << offset))) {
>
>
> Is wrong. You're looking for an unset span of order bits at a given
> offset. So you get the byte offset for the first, then all the
> following bitmap[n] need to be zero until you need to do an offset in
> reverse for the last bit. i.e. (assuming BITS_PER_LONG=32) for a span
> of 126 at offset 1, you check
>
> bitmap[0] & 0xfffffffe == 0
> bitmap[1] & 0xffffffff == 0
> bitmap[2] & 0xffffffff == 0
> bitmap[3] & 0x7fffffff == 0
>
> and so on.
>
This code operates on the assumption that offset is always 0 for the
pages == BITS_PER_LONG case. It's calculated in this order:
unsigned int pages = 1 << order;
int i;
int span = (pages + (BITS_PER_LONG - 1)) / BITS_PER_LONG;
if (pages > BITS_PER_LONG)
pages = BITS_PER_LONG;
...
for (i = 0; i < bits; i += pages) {
int index = i/BITS_PER_LONG;
int offset = i - (index * BITS_PER_LONG);
...
So in the case of pages >= BITS_PER_LONG the mask will be 0xffffffff, and
offset will be 0, and the span will define how many adjacent words we
need to set. Unless I'm missing something, I don't see how your case
would happen. I did test this quite a bit mixing both tiny and large
orders.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-20 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 1:48 [PATCH] bitmap: Support for pages > BITS_PER_LONG Paul Mundt
2006-01-19 3:11 ` Paul Jackson
2006-01-20 3:28 ` James Bottomley
2006-01-20 7:28 ` Paul Mundt [this message]
2006-01-20 9:10 ` Paul Jackson
2006-01-19 6:07 ` Paul Jackson
2006-01-19 6:40 ` Paul Jackson
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=20060120072851.GA3918@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=jamey.hicks@hp.com \
--cc=joshua@joshuawise.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rmk@arm.linux.org.uk \
--cc=spyro@f2s.com \
--cc=tony@atomide.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.