From: Thomas Gleixner <tglx@linutronix.de>
To: "Jörn Engel" <joern@logfs.org>
Cc: matthieu castet <castet.matthieu@free.fr>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-mtd@lists.infradead.org
Subject: Re: LogFS merge
Date: Sun, 4 May 2008 18:20:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0805041809370.3318@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080503120005.GA32608@logfs.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 708 bytes --]
On Sat, 3 May 2008, Jörn Engel wrote:
> 1.
> Ubifs takes the easy approach and uses ubi for wear leveling, bad block
> handling, ets. Saves a ton of work, gives quick results and is limited
> by ubi scan time, which is O(n).
Which is easy enough to fix.
> Logfs ignores ubi and does wear leveling, bad block handling, etc.
> itself. Bad block handling in particular is not too robust yet. If you
> expect blocks to rot away after mkfs time, logfs is a bad choice.
It's a matter of fact that especially on NAND flash blocks become bad
over time, i.e. after mkfs. So that's a pretty crucial feature which
needs to be complete and robust before it's declared to be usable on
such devices.
Thanks,
tglx
next prev parent reply other threads:[~2008-05-04 16:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 9:29 matthieu castet
2008-05-03 12:00 ` Jörn Engel
2008-05-04 16:20 ` Thomas Gleixner [this message]
2008-05-04 18:04 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 13:32 Jörn Engel
2008-05-02 14:49 ` Pekka Enberg
2008-05-02 15:31 ` Christoph Hellwig
2008-05-02 20:33 ` Jörn Engel
2008-05-02 16:52 ` Arnd Bergmann
2008-05-02 21:47 ` Jörn Engel
2008-05-02 17:17 ` Linus Torvalds
2008-05-02 20:21 ` Jörn Engel
2008-05-02 20:33 ` Linus Torvalds
2008-05-02 21:31 ` Jörn Engel
2008-05-02 21:39 ` Linus Torvalds
2008-05-02 21:58 ` Jörn Engel
2008-05-03 7:03 ` Willy Tarreau
2008-05-03 9:11 ` Adrian Bunk
2008-05-03 9:18 ` Willy Tarreau
2008-05-03 9:37 ` Adrian Bunk
2008-05-03 9:44 ` Pekka Enberg
2008-05-03 11:06 ` Adrian Bunk
2008-05-03 17:16 ` Linus Torvalds
2008-05-02 17:29 ` Andi Kleen
2008-05-02 21:34 ` Jörn Engel
2008-05-05 20:31 ` 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=alpine.LFD.1.10.0805041809370.3318@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=castet.matthieu@free.fr \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome