From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: linux-mtd@lists.infradead.org
Subject: Re: choosing a file system to use on NAND/UBI
Date: Fri, 28 Mar 2008 09:22:44 +0200 [thread overview]
Message-ID: <47EC9CC4.3090902@nokia.com> (raw)
In-Reply-To: <20080328010403.GB23610@cloud.net.au>
Hamish Moffatt wrote:
> I'm developing an embedded product which will have its root file system
> on NAND. The root will be pre-prepared and installed using
> flashcp/nandwrite/ubiupdatevol, and usually mounted read-only.
> Occasionally we might want to mount it read/write for debug purposes.
>
> I'm intending to use UBI for volume management and wear-levelling.
>
> JFFS2 on UBI does not seem very fast, in particular mount time and
> initial access (until cache is populated). I tried disabling compression
> but that seemed to make it worse (mount time was doubled).
Do you know that you need to have JFFS2 summary support enabled to have
reasonable mount times?
prev parent reply other threads:[~2008-03-28 7:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 1:04 choosing a file system to use on NAND/UBI Hamish Moffatt
2008-03-28 6:33 ` Artem Bityutskiy
2008-04-07 5:12 ` Hamish Moffatt
2008-04-07 7:13 ` Artem Bityutskiy
2008-04-07 7:32 ` Hamish Moffatt
2008-04-07 7:48 ` Hamish Moffatt
2008-04-07 7:56 ` Artem Bityutskiy
2008-04-07 11:20 ` Hamish Moffatt
2008-04-07 12:15 ` Artem Bityutskiy
2008-04-07 12:16 ` Artem Bityutskiy
2008-04-07 12:22 ` Hamish Moffatt
2008-04-07 12:44 ` Artem Bityutskiy
2008-04-07 15:31 ` Jamie Lokier
2008-04-08 10:21 ` Hamish Moffatt
2008-04-07 8:41 ` Artem Bityutskiy
2008-04-08 7:07 ` Artem Bityutskiy
2008-03-28 7:22 ` Adrian Hunter [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=47EC9CC4.3090902@nokia.com \
--to=ext-adrian.hunter@nokia.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 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.