From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Cc: Han Chang <posaune@hotmail.com>
Subject: Re: FAT vs jFFS2 for NAND.
Date: Sun, 28 May 2006 17:54:26 +1200 [thread overview]
Message-ID: <200605281754.26258.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <BAY110-F408C270588868018C9B3D3BC9C0@phx.gbl>
On Sunday 28 May 2006 14:58, Han Chang wrote:
> Hi there,
>
> My first question is that if I can use FAT file system for NAND. If yes,
> what are the pros and cons for using FAT vs. JFFS2.
FAT needs to work with a block driver, so you can use FAT if you use a block
driver on top of the NAND.
You can use JFFS2 or YAFFS as true flash file systems (ie that work directly
with the NAND).
Pros of FAT:
*) If you're using this on a device that must look like a USB mass storage
device, or similar, then FAT is easier for people to use.
*) Have a smaller RAM footprint than JFFS2 or YAFFS. JFFS2 and YAFFS both use
ram to build runtime look-up trees.
*) FAT file systems will typically mount faster than JFFS2 and YAFFS, though
both YAFFS and JFFS2 mount times have reduced significantly in recent weeks.
Pros of YAFFS or JFFS2:
*) Faster. YAFFS is faster than JFFS2 which should be faster than FAT.
*) YAFFS and JFFS2 are both log structured fs which make them far more robust
against corruption than FAT.
*) YAFFS abd JFFS2 support features like links which are missing from FAT.
-- Charles
next prev parent reply other threads:[~2006-05-28 5:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 2:58 FAT vs jFFS2 for NAND Han Chang
2006-05-28 5:54 ` Charles Manning [this message]
2006-06-15 0:34 ` Han Chang
2006-06-15 7:53 ` Thomas Gleixner
2006-06-19 18:31 ` Han Chang
2006-06-19 18:38 ` Thomas Gleixner
2006-06-19 20:23 ` David Woodhouse
2006-06-19 21:10 ` Charles Manning
2006-06-20 11:31 ` Claudio Lanconelli
2006-06-20 12:30 ` David Woodhouse
2006-06-20 13:25 ` Claudio Lanconelli
2006-06-20 13:52 ` Thomas Gleixner
2006-06-20 17:26 ` Claudio Lanconelli
2006-06-20 17:41 ` Thomas Gleixner
2006-06-21 14:15 ` Claudio Lanconelli
2006-06-21 18:19 ` Thomas Gleixner
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=200605281754.26258.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=linux-mtd@lists.infradead.org \
--cc=posaune@hotmail.com \
/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