From: Artem Bityutskiy <dedekind@yandex.ru>
To: Willy Tarreau <w@1wt.eu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Andi Kleen" <andi@firstfloor.org>,
"Tomasz Chmielewski" <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>,
penberg@cs.helsinki.fi, "Jörn Engel" <joern@logfs.org>,
ext-adrian.hunter@nokia.com, jwboyer@gmail.com
Subject: Re: UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system)
Date: Wed, 02 Apr 2008 10:17:14 +0300 [thread overview]
Message-ID: <47F332FA.9000603@yandex.ru> (raw)
In-Reply-To: <20080402062543.GA5950@1wt.eu>
Willy Tarreau wrote:
> One of the problem is that unless you crash-test your flash cards, you will
> never know if their wear-leveling algorithm is fine or not. And I suspect
> that nowadays, due to very large consumer demand, flash cards price drop
> at the cost of reliability. I think that most of those not flagged
> "industrial-grade" do absolutely zero wear-leveling, because they are sold
> to people using them in digital cameras, and they will never kill their
> device with such a usage.
Sure, I know about this problem. My point was that in this case it is wiser
to use bare flash and put JFFS2 on it, instead of using this black box
MMC/etc and then put JFFS2 on it.
> I'm certainly not the only one with this requirement. A lot of embedded
> motherboards come with IDE compactflash connectors. This is very convenient,
> but if you need to keep informations between reboots, you have to write to
> the device anyway. If you need to do that very often, either you pray for
> the device to be very reliable, or you take all the chances on your side
> by adding your own wear-leveling "just in case".
OK. Fair enough. Although stuff exists, but this does not necessarily mean
this a good design :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2008-04-02 7:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 8:02 UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system) Tomasz Chmielewski
2008-04-01 8:45 ` Artem Bityutskiy
2008-04-01 9:03 ` Jörn Engel
2008-04-01 9:09 ` Artem Bityutskiy
2008-04-01 9:31 ` Jörn Engel
2008-04-01 9:39 ` Tomasz Chmielewski
2008-04-01 9:57 ` Artem Bityutskiy
2008-04-02 14:17 ` Tomasz Chmielewski
2008-04-02 14:22 ` Jörn Engel
2008-04-01 11:06 ` Andi Kleen
2008-04-01 11:23 ` Artem Bityutskiy
2008-04-01 16:27 ` H. Peter Anvin
2008-04-01 21:26 ` Willy Tarreau
2008-04-02 4:47 ` Artem Bityutskiy
2008-04-02 6:25 ` Willy Tarreau
2008-04-02 7:17 ` Artem Bityutskiy [this message]
2008-04-09 21:09 ` Pavel Machek
2008-04-09 21:32 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2008-03-27 14:55 [RFC PATCH] UBIFS - new flash file system Artem Bityutskiy
2008-03-31 12:29 ` Jan Engelhardt
2008-03-31 12:47 ` Adrian Hunter
2008-03-31 13:20 ` Jörn Engel
2008-04-01 5:26 ` UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system) Artem Bityutskiy
2008-04-01 5:28 ` Artem Bityutskiy
2008-04-01 5:56 ` Artem Bityutskiy
2008-04-01 9:25 ` Jörn Engel
2008-04-01 9:39 ` Artem Bityutskiy
2008-04-01 10:51 ` Jörn Engel
2008-04-01 11:17 ` Artem Bityutskiy
2008-04-01 9:19 ` Jörn Engel
2008-04-01 9:46 ` Artem Bityutskiy
2008-04-01 11:16 ` Jörn Engel
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=47F332FA.9000603@yandex.ru \
--to=dedekind@yandex.ru \
--cc=andi@firstfloor.org \
--cc=ext-adrian.hunter@nokia.com \
--cc=hpa@zytor.com \
--cc=joern@logfs.org \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=penberg@cs.helsinki.fi \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.