From: Artem Bityutskiy <dedekind@infradead.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: AMIT KUMARSHARMA <amitsharma.9@samsung.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Adrian Hunter <ext-adrian.hunter@nokia.com>,
Corentin Chary <corentin.chary@gmail.com>,
Brijesh Singh <brij.singh@samsung.com>
Subject: Re: Regarding UBI scalability
Date: Mon, 09 Feb 2009 10:46:22 +0200 [thread overview]
Message-ID: <1234169182.17790.92.camel@localhost.localdomain> (raw)
In-Reply-To: <9c9fda240902080231r51c4bcf3o37c0044bf9d924ee@mail.gmail.com>
On Sun, 2009-02-08 at 19:31 +0900, Kyungmin Park wrote:
> One more requested feature.
> How about to scan ubi image and bad block table at simultaneously?
> Now there's two full device scan, bbt and ubi at booting time.
> As internal LEA mapping layout, how about to add bbt layout?
>
> It's also helpful to MLC since MLC doesn't have read oob so it calls
> page read command to build bbt.
> As you know it takes long time.
>
> I'm not sure if internal LEA maping is supported, it's meaningful work or not.
>
> How do you think?
Well, doing scanning twice is not very good indeed. I guess what you
could do is to make MTD avoid scanning and building the bad block
table at all and build it lazily. But then you need 2 bits per
eraseblock, not just one. IOW, sure, it is possible to optimize this.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-02-09 8:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7824366.270131233573513030.JavaMail.weblogic@epml10>
2009-02-04 9:47 ` Regarding UBI scalability Adrian Hunter
2009-02-05 9:40 ` Brijesh Singh
2009-02-08 9:48 ` Corentin Chary
2009-02-08 10:31 ` Kyungmin Park
2009-02-09 8:46 ` Artem Bityutskiy [this message]
2009-01-30 12:45 BRIJESH SINGH
2009-02-02 9:31 ` Artem Bityutskiy
2009-02-02 10:17 ` Amit Kumar Sharma
2009-02-02 11:07 ` Adrian Hunter
2009-02-02 10:57 ` Artem Bityutskiy
2009-02-02 11:18 ` Adrian Hunter
2009-02-02 20:07 ` Jamie Lokier
2009-02-02 23:44 ` Corentin Chary
2009-02-03 10:35 ` Brijesh Singh
2009-02-03 10:48 ` Artem Bityutskiy
2009-02-03 11:27 ` Enrico Scholz
2009-02-04 7:41 ` Artem Bityutskiy
2009-02-04 9:29 ` Adrian Hunter
2009-02-05 9:37 ` Brijesh Singh
2009-02-05 11:17 ` Adrian Hunter
2009-02-11 7:50 ` Brijesh Singh
2009-02-03 10:46 ` Artem Bityutskiy
2009-02-03 11:13 ` Corentin Chary
2009-02-03 11:51 ` Brijesh Singh
2009-02-04 7:45 ` 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=1234169182.17790.92.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=amitsharma.9@samsung.com \
--cc=brij.singh@samsung.com \
--cc=corentin.chary@gmail.com \
--cc=ext-adrian.hunter@nokia.com \
--cc=kmpark@infradead.org \
--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.