From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>,
linux-mtd@lists.infradead.org
Subject: Re: JFFS2 access delay
Date: Wed, 25 May 2005 12:06:14 +0200 [thread overview]
Message-ID: <20050525100614.GA17002@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1117009669.13088.2.camel@sauron.oktetlabs.ru>
On Wed, 25 May 2005 12:27:49 +0400, Artem B. Bityuckiy wrote:
>
> > Do you know if JFFS3 or Yaffs show a similar behaviour?
> >
> JFFS3 doesn't really exist.
> I haven't ever tried YAFFS, but Charles said it is OK.
If you read the design, you notice the same scalability problem JFFS2
suffers from. Yaffs is maybe 10x or 100x better. Which means, it
will be just as bad as JFFS2 is today once the flash sizes have grown
by 10x or 100x.
And in exchange it suffers a bunch of other limittions. Basically,
only use it if you have an embedded device with raw nand flash access.
WRT. flash filesystems, you're currently sitting between a rock and a
hard place. Traditional disk-based filesystems like ext2 will kill
your flash in a few month or even weeks, but show decent performance.
Dedicated flash filesystems are near-optimal for flash survival and
perform like a snail on an uphill race.
For now, go with JFFS2 or Yaffs (if you have NAND and don't need
compression).
Jörn
--
A victorious army first wins and then seeks battle.
-- Sun Tzu
prev parent reply other threads:[~2005-05-25 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 12:40 JFFS2 access delay "David Müller (ELSOFT AG)"
2005-05-24 14:13 ` Artem B. Bityuckiy
2005-05-25 8:01 ` "David Müller (ELSOFT AG)"
2005-05-25 8:14 ` Artem B. Bityuckiy
2005-05-24 14:55 ` Jörn Engel
2005-05-25 8:02 ` "David Müller (ELSOFT AG)"
2005-05-25 8:27 ` Artem B. Bityuckiy
2005-05-25 10:06 ` Jörn Engel [this message]
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=20050525100614.GA17002@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=d.mueller@elsoft.ch \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.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