From: Adrian Hunter <adrian.hunter@nokia.com>
To: Bosi Daniele <Daniele.Bosi@mta.it>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: UBI FS mounting time
Date: Wed, 22 Jul 2009 09:44:23 +0300 [thread overview]
Message-ID: <4A66B547.6020207@nokia.com> (raw)
In-Reply-To: <531B6536C9F737458807DF75064873C8303DD7D768@mta-digimail.MTA.INT>
Bosi Daniele wrote:
> We have a UBI+UBIFS 1GB partition on a NAND chip, which takes around 6s to mount.
>
> We'd like to have the data available at least read-only earlier than that.
>
> We know UBI on principle needs to read the map of all blocks in order to rebuild the logical view of the memory, but maybe there's another way around it to make it available earlier...
>
> Someone know how?
Some options are:
a) Use another smaller partition that can mount first and provide some functionality while the larger partition mounts.
b) Reduce the number of eraseblocks by combining them into larger logical blocks.
c) Change UBI to write its mapping table when it is unloaded, so it can be read quickly when loading (still have to scan if UBI was not unloaded cleanly).
next prev parent reply other threads:[~2009-07-22 6:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 17:00 UBI FS mounting time Bosi Daniele
2009-07-22 6:44 ` Adrian Hunter [this message]
2009-07-22 7:12 ` Corentin Chary
2009-07-22 7:38 ` Adrian Hunter
2009-07-22 7:57 ` Corentin Chary
2009-07-22 8:12 ` Adrian Hunter
2009-07-22 8:30 ` Artem Bityutskiy
2009-07-22 8:36 ` Artem Bityutskiy
2009-07-22 9:34 ` Jamie Lokier
2009-07-22 7:22 ` Canella Matteo
2009-07-22 8:10 ` Canella Matteo
2009-07-22 9:19 ` Adrian Hunter
2009-07-22 14:32 ` LEB size configuration (was: UBI FS mounting time) Canella Matteo
2009-07-22 14:53 ` LEB size configuration Artem Bityutskiy
2009-07-22 15:12 ` Canella Matteo
2009-07-22 15:15 ` Artem Bityutskiy
2009-07-22 9:30 ` UBI FS mounting time Artem Bityutskiy
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=4A66B547.6020207@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=Daniele.Bosi@mta.it \
--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;
as well as URLs for NNTP newsgroup(s).