[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080331134004.GA465@logfs.org>
Date: Mon, 31 Mar 2008 15:40:04 +0200
From: Jörn Engel <joern@...fs.org>
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
LKML <linux-kernel@...r.kernel.org>,
Adrian Hunter <ext-adrian.hunter@...ia.com>,
joern@...ybastard.org
Subject: Re: [RFC PATCH] UBIFS - new flash file system
On Mon, 31 March 2008 14:29:59 +0200, Jan Engelhardt wrote:
> On Thursday 2008-03-27 15:55, Artem Bityutskiy wrote:
> >
> >here is a new flash file system developed by Nokia engineers with
> >help of the University of Szeged. The new file-system is called
> >UBIFS, which stands for UBI file system. UBI is the wear-leveling/
> >bad-block handling/volume management layer which is already in
> >mainline (see drivers/mtd/ubi).
> >[...]
>
> And how does it compare to logfs?
Both share similar design goals. Biggest difference is that ubifs works
on top of ubi and depends on ubi support, while logfs works on plain mtd
(or block devices) and does everything itself.
Code size difference is huge. Ubi weighs some 11kloc, ubifs some 30,
logfs some 8.
Ubi scales linearly, as it does a large scan at init time. It is still
reasonably fast, as it reads just a few bytes worth of header per block.
Logfs mounts in O(1) but will currently become mindbogglingly slow when
the filesystem nears 100% full and write are purely random. Not that
any other flash filesystem would perform well under these conditions -
it is the known worst case scenario.
Jörn
--
Victory in war is not repetitious.
-- Sun Tzu
--
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