[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20071125232953.GF114266761@sgi.com>
Date: Mon, 26 Nov 2007 10:29:53 +1100
From: David Chinner <dgc@....com>
To: Nick Piggin <nickpiggin@...oo.com.au>
Cc: David Chinner <dgc@....com>, xfs-oss <xfs@....sgi.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/9]: introduce radix_tree_gang_lookup_range
On Mon, Nov 26, 2007 at 10:17:24AM +1100, Nick Piggin wrote:
> On Thursday 22 November 2007 11:32, David Chinner wrote:
> > Introduce radix_tree_gang_lookup_range()
> >
> > The inode clustering in XFS requires a gang lookup on the radix tree to
> > find all the inodes in the cluster. The gang lookup has to set the
> > maximum items to that of a fully populated cluster so we get all the
> > inodes in the cluster, but we only populate the radix tree sparsely (on
> > demand).
> >
> > As a result, the gang lookup can search way, way past the index of end
> > of the cluster because it is looking for a fixed number of entries to
> > return.
> >
> > We know we want to terminate the search at either a specific index or a
> > maximum number of items, so we need to add a "last_index" parameter to
> > the lookup.
>
> Yeah, this fixes one downside of the gang lookup API. For consistency
> it would be nice to do this for the tag lookup API as well...
Sure, I have need to do that as well. ;)
> > Furthermore, the existing radix_tree_gang_lookup() can use this same
> > function if we define a RADIX_TREE_MAX_INDEX value so the search is not
> > limited by the last_index.
>
> Nit: should just define it to be ULONG_MAX.
Oh, right. Silly me. I'll post updated radix tree patches later today.
Thanks, Nick.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists