From: David Woodhouse <dwmw2@infradead.org>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Q: Filesystem choice..
Date: Mon, 26 Jan 2004 06:42:09 +0000 [thread overview]
Message-ID: <1075099329.17157.97.camel@lapdancer.baythorne.internal> (raw)
In-Reply-To: <m3u12jr8y4.fsf@maxwell.lnxi.com>
On Sun, 2004-01-25 at 14:53 -0700, Eric W. Biederman wrote:
> The old papers on jffs2 would make it unacceptable as it reserves
> 5 erase blocks.
It's got slightly different heuristics now -- a proportion of total
size, plus a proportion of total _blocks_. That was done primarily to
deal with NAND flash, where we need _more_ blocks reserved, but it
should also have helped with small NOR flashes.
You blatantly don't _need_ to reserve five erase blocks to let you
rewrite the contents of the remaining, erm, one erase block full of
data. You can tune this; it's not a mount option but it's relatively
simple to change in the code.
> And I don't know if yaffs or yaffs2 is any better.
They're for NAND, not NOR flash.
> In addition boot time is important so it would be ideal if I did not
> to read every byte of the ROM chip to initialize the filesystem.
There have been efforts to improve JFFS2 performance in this respect. It
still reads the _header_ from each node of the file system, but doesn't
actually checksum every node any more.
--
dwmw2
next prev parent reply other threads:[~2004-01-26 6:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 21:53 Q: Filesystem choice Eric W. Biederman
2004-01-25 22:49 ` Jörn Engel
2004-01-26 6:42 ` David Woodhouse [this message]
2004-01-26 7:09 ` Eric W. Biederman
2004-01-26 7:40 ` David Woodhouse
2004-01-26 8:34 ` Joakim Tjernlund
2004-01-26 8:38 ` David Woodhouse
2004-01-26 9:28 ` Joakim Tjernlund
2004-01-26 9:23 ` Eric W. Biederman
2004-01-26 9:31 ` David Woodhouse
2004-01-26 16:20 ` Eric W. Biederman
2004-01-26 15:32 ` Jörn Engel
2004-01-27 4:30 ` Charles Manning
2004-01-27 7:13 ` Eric W. Biederman
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=1075099329.17157.97.camel@lapdancer.baythorne.internal \
--to=dwmw2@infradead.org \
--cc=ebiederman@lnxi.com \
--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