[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0901100429h415d3a87o40ba4849120832c8@mail.gmail.com>
Date: Sat, 10 Jan 2009 21:29:04 +0900
From: "KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
To: "Johannes Berg" <johannes@...solutions.net>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Linux Kernel list" <linux-kernel@...r.kernel.org>,
"Jörn Engel" <joern@...fs.org>
Subject: Re: [PATCH] add b+tree library
>> > This adds a b+tree library. The API and memory layout is documented in
>> > the header file lib/btree.h. There are tree versions for 32, 64 and
>> > 128 bit keys as well as unsigned long (32/64 depending on platform).
>>
>> Can this library remove the btree code in some btree based filesystem?
>
> Joern is going to use it for logfs, that's the point. Not sure about
> other filesystems.
Why can't you investigate other filesystem?
if this library is used by only one fs, why does this library routine
need to linux/lib/ directory?
--
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