From: Matthieu CASTET <matthieu.castet@parrot.com>
To: dedekind@infradead.org
Cc: Nancy <nancydreaming@gmail.com>,
linux-mtd@lists.infradead.org, Bruce_Leonard@selinc.com
Subject: Re: [RFC] slight UBI scan time improvement
Date: Wed, 23 Apr 2008 11:21:19 +0200 [thread overview]
Message-ID: <480EFF8F.40204@parrot.com> (raw)
In-Reply-To: <1208938864.11721.44.camel@sauron>
Artem Bityutskiy wrote:
> Hi,
>>>
>>> Hamish
>> Do you know when the bad block scanning finish and the ubi scan start ?
>
> Good point Matthieu. Indeed, _at least_ 1.23 sec is spend in the driver
> for scanning against bad eraseblocks to build in-memory bad block table
> (BBT). And it is probably more than 1.23 sec. If you start using
> on-flash bad block table, this should go away. I never used on-flash
> BBT, but I know MTD supports this and for example OLPC has on-flash BBT.
>
May be UBI should print a message at startup.
Matthieu
next prev parent reply other threads:[~2008-04-23 9:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 16:42 [RFC] slight UBI scan time improvement Artem Bityutskiy
2008-04-22 17:28 ` Bruce_Leonard
2008-04-22 18:07 ` Artem Bityutskiy
2008-04-23 7:15 ` Nancy
2008-04-23 7:32 ` Artem Bityutskiy
2008-04-23 8:01 ` Nancy
2008-04-23 8:16 ` Artem Bityutskiy
2008-04-23 9:07 ` Nancy
2008-04-23 9:13 ` Artem Bityutskiy
2008-04-23 10:51 ` Nancy
2008-04-23 10:57 ` Nancy
2008-04-23 12:24 ` Artem Bityutskiy
2008-04-23 12:23 ` Artem Bityutskiy
2008-04-23 7:38 ` Hamish Moffatt
2008-04-23 8:13 ` Matthieu CASTET
2008-04-23 8:21 ` Artem Bityutskiy
2008-04-23 9:21 ` Matthieu CASTET [this message]
2008-04-23 9:27 ` Artem Bityutskiy
2008-04-23 12:40 ` Hamish Moffatt
2008-04-23 12:57 ` Artem Bityutskiy
2008-04-23 13:42 ` Hamish Moffatt
2008-04-23 14:09 ` Artem Bityutskiy
2008-04-24 1:53 ` Hamish Moffatt
2008-04-24 6:21 ` Artem Bityutskiy
2008-04-24 7:02 ` Hamish Moffatt
2008-04-24 0:10 ` Hamish Moffatt
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=480EFF8F.40204@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=Bruce_Leonard@selinc.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nancydreaming@gmail.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 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.