From: Artem Bityutskiy <dedekind@infradead.org>
To: Brijesh Singh <brijesh.s.singh@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI bad block Management
Date: Wed, 14 Feb 2007 14:51:58 +0200 [thread overview]
Message-ID: <1171457518.8593.6.camel@sauron> (raw)
In-Reply-To: <6b5362aa0702140128h69cc8f11k48bec5b739640ded@mail.gmail.com>
Hi,
On Wed, 2007-02-14 at 14:58 +0530, Brijesh Singh wrote:
> Hi,
> The flash devices are getting of bigger in Size.The Init Scan time
> will increase with bigger Size flash.How long are we going to rely on
> MTD for Bad block Management.Even MTD doesn't maintain List but calls
> the hardware, if hardware supports it.
> This can be done in two ways,
> 1:) Straight right the bitmap,and if changed erase it.We can do it in
> One reserved block.
> If allowed bad blocks are 20%,it will be erased 20% times
> of total PEB count.
> 2:)Keep a Queue in Scan of Bad blocks.Ec header contains one field
> called last bad block.Which is PEb no.So if block is found bad,next
> block to be written first will have Bad block no in EC.So it is
> maintained across reboots.
> 3:)Keep a Log in reserved Block.When it is getting full,create bitmap
> and write it on the block.This will reduce the erasing of that block.
>
> So we can maintain Bad block Map in UBI if it is necessary.
I really tried to realize what you mean, but failed, sorry. I do not
understand at all what are you about. May you re-phrase?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2007-02-14 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 9:28 UBI bad block Management Brijesh Singh
2007-02-14 9:31 ` Artem Bityutskiy
2007-02-14 12:51 ` Artem Bityutskiy [this message]
2007-02-15 5:40 ` Brijesh Singh
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=1171457518.8593.6.camel@sauron \
--to=dedekind@infradead.org \
--cc=brijesh.s.singh@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 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.