From: Konstantin Baydarov <kbaidarov@dev.rtsoft.ru>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] NAND: Lazily BBT construction
Date: Fri, 24 Nov 2006 16:56:18 +0300 [thread overview]
Message-ID: <20061124165618.44418a5e@localhost.localdomain> (raw)
In-Reply-To: <1164373550.576.13.camel@sauron>
On Fri, 24 Nov 2006 15:05:50 +0200
Artem Bityutskiy <dedekind@infradead.org> wrote:
> On Fri, 2006-11-24 at 15:42 +0300, Konstantin Baydarov wrote:
> > This is the implementation of lazy BBT construction. It introduces
> > a new config option that allows to construct BBT(bad block table)
> > lazily for NAND chips with memory based BBT.
> > The main goal of the feature introduced is to decrease boot time.
> > How it works: BBT is filled only when we check if block is bad. NAND
> > is
> > scanned and BBT entries is constructed from topmost unscanned block
> > to requested.
> > By default BBT is constructed during boot. To enable lazily
> > construction NAND_LAZY_BBT bit should be set in options field of
> > structure nand_chip.
>
> Also, the 3rd question.
>
> 3. Why don't you use on-flash BBT if you are not satisfied with in-RAM
> BBT?
>
Patch covers the case when there is no on-flash BBT and on-flash
BBT wasn't requested (don't need to write to chip Memory BBT after
construction). How can I use it? Also when we have on-flash BBT we
don't need to scan chip so we don't need lazily BBT.
next prev parent reply other threads:[~2006-11-24 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 12:42 [PATCH] [MTD] NAND: Lazily BBT construction Konstantin Baydarov
2006-11-24 13:01 ` Artem Bityutskiy
2006-11-24 13:11 ` Vitaly Wool
2006-11-24 15:42 ` Artem Bityutskiy
2006-11-24 13:05 ` Artem Bityutskiy
2006-11-24 13:56 ` Konstantin Baydarov [this message]
2006-11-24 15: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=20061124165618.44418a5e@localhost.localdomain \
--to=kbaidarov@dev.rtsoft.ru \
--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