From: Artem Bityutskiy <dedekind1@gmail.com>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Bosi Daniele <Daniele.Bosi@mta.it>,
Corentin Chary <corentin.chary@gmail.com>,
Brijesh Singh <brij.singh@samsung.com>
Subject: Re: UBI FS mounting time
Date: Wed, 22 Jul 2009 11:30:35 +0300 [thread overview]
Message-ID: <1248251435.24676.42.camel@localhost> (raw)
In-Reply-To: <4A66CA03.5000406@nokia.com>
On Wed, 2009-07-22 at 11:12 +0300, Adrian Hunter wrote:
> I would fix the anchor block in the first good PEB and use just one.
> If you lose power while erasing the anchor then you have to scan,
> but you have to scan anyway if you lose power, so there is not much
> difference.
But if you go this far, an implement the anchor things, then it makes
much more sense to implement your UBI2 ides, instead of this crippled
"dump everything to flash on unmount" stuff. Your idea of a journal
is much saner. Remember you suggested it to Samsung people as a way to
fix mount time problems, but not memory consumption issuse, which are
not that bad, and then you said we can create UBI3 to fix memory issues.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-07-22 8:31 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
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 [this message]
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=1248251435.24676.42.camel@localhost \
--to=dedekind1@gmail.com \
--cc=Daniele.Bosi@mta.it \
--cc=adrian.hunter@nokia.com \
--cc=brij.singh@samsung.com \
--cc=corentin.chary@gmail.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;
as well as URLs for NNTP newsgroup(s).