[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070516052253.GI943@1wt.eu>
Date: Wed, 16 May 2007 07:22:54 +0200
From: Willy Tarreau <w@....eu>
To: Jörn Engel <joern@...ybastard.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mtd@...ts.infradead.org, Albert Cahalan <acahalan@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jan Engelhardt <jengelh@...ux01.gwdg.de>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
Pekka Enberg <penberg@...helsinki.fi>,
Greg KH <greg@...ah.com>, Ingo Oeser <ioe-lkml@...eria.de>
Subject: Re: [PATCH] LogFS take three
On Wed, May 16, 2007 at 02:06:31AM +0200, Jörn Engel wrote:
> On Tue, 15 May 2007 13:37:59 -0700, Andrew Morton wrote:
> > It's strange and a bit regrettable that an fs would have dependency on MTD,
> > really.
>
> It is and changing this wouldn't be too hard. All device access goes
> through five functions (read, write, erase, is_bad and mark_bad). As
> soon as someone seriously cares I will add a struct logfs_device_ops and
> have a second set of these functions for block devices.
>
> On hard disks it shouldn't make too much sense. The filesystem will
> fragment like a splinter bomb and be just as popular.
On hard disks, yes, but as you suggested, there are lots of other flash
devices interfaced as block devices. CompactFlash comes to mind, USB
keys too. And on these ones, the most important is to reduce the number
of writes and to support large sizes. I already see LogFS as an interesting
alternative to JFFS2 on such devices, eventhough it does not (yet?) support
compression.
Regards,
Willy
-
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