From: Andrew Morton <akpm@osdl.org>
To: jim.houston@comcast.net
Cc: kevcorry@us.ibm.com, linux-kernel@vger.kernel.org,
dm-devel@redhat.com, torvalds@osdl.org, agk@redhat.com
Subject: Re: [PATCH] 1/1: Device-Mapper: Remove 1024 devices limitation
Date: Wed, 7 Jul 2004 04:10:59 -0700 [thread overview]
Message-ID: <20040707041059.17287591.akpm@osdl.org> (raw)
In-Reply-To: <1089197914.986.17.camel@new.localdomain>
Jim Houston <jim.houston@comcast.net> wrote:
>
> On Tue, 2004-07-06 at 19:16, Andrew Morton wrote:
> Jim Houston <jim.houston@comcast.net> wrote:
> > >
> > > With out the test above an id beyond the allocated space will alias
> > > to one that exists. Perhaps the highest id currently allocated is
> > > 100, there will be two layers in the radix tree and the while loop
> > > above will only look at the 10 least significant bits. If you call
> > > idr_find with 1025 it will return the pointer associated with id 1.
> >
> > OK.
> >
> > > The patch I sent was against linux-2.6.7, so I missed the change to
> > > MAX_ID_SHIFT.
> >
> > How about this?
> >
> > n = idp->layers * IDR_BITS;
> > + if (id >= (1 << n))
> > + return NULL;
> > +
> > p = idp->top;
> > +
> > /* Mask off upper bits we don't use for the search. */
> > id &= MAX_ID_MASK;
> >
>
> Hi Andrew,
>
> It's not quite right. If you want to keep a count in the upper bits
> you have to mask off that count before checking if the id is beyond the
> end of the allocated space.
OK, I'll fix that up.
But I don't want to keep a count in the upper bits! I want rid of that
stuff altogether, completely, all of it. It just keeps on hanging around :(
We should remove MAX_ID_* from the kernel altogether.
next prev parent reply other threads:[~2004-07-07 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 15:35 [PATCH] 1/1: Device-Mapper: Remove 1024 devices limitation Kevin Corry
2004-07-01 21:38 ` Andrew Morton
2004-07-02 2:54 ` Kevin Corry
2004-07-02 3:30 ` Andrew Morton
2004-07-02 17:33 ` Kevin Corry
2004-07-02 19:42 ` Andrew Morton
2004-07-06 18:23 ` Kevin Corry
2004-07-06 21:23 ` Andrew Morton
2004-07-06 21:35 ` Alasdair G Kergon
2004-07-06 22:04 ` Alasdair G Kergon
2004-07-06 22:20 ` Andrew Morton
2004-07-06 22:07 ` Jim Houston
2004-07-06 22:28 ` Andrew Morton
2004-07-06 23:00 ` Jim Houston
2004-07-06 23:16 ` Andrew Morton
2004-07-07 10:58 ` Jim Houston
2004-07-07 11:10 ` Andrew Morton [this message]
2004-07-12 14:49 ` Kevin Corry
2004-07-12 18:14 ` Andrew Morton
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=20040707041059.17287591.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jim.houston@comcast.net \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.