[PATCH][MTD][NAND]Bad Block Management

Frans Meulenbroeks fransmeulenbroeks at gmail.com
Thu Aug 28 05:06:42 EDT 2008

2008/8/27 David Woodhouse <dwmw2 at infradead.org>:
> On Wed, 2008-08-27 at 12:59 +0200, Frans Meulenbroeks wrote:
>> Wrt the device wise approach: I think I would prefer if I could say
>> per partition if I wanted to use this (and thus have the mapping done
>> per partition). That way filesystems that do their own bad block
>> handling can do it the way they want to.Now it seems a little bit
>> double work to have bad block handling in both the filesystem and in
>> the mtd layer.
> I don't believe it lives in the low-level MTD drivers. The _users_ (file
> system code, translation layers, etc.) of devices should handle this as
> they see fit (although we can provide _library_ code for them to use if
> they want to). I don't think it lives in the NAND driver though.

As this is reply to my msg, is this directed to me?
If so: yes I am definitely in favour of modularisation, separation of
concerns etc (that is if it does not hamper performance too much).
Then again: as far as I can see it the patch from Zhao is a patch in
the driver level.

Wrt bad block handling etc. Guess this can be done in ftl or so (I'm
not really an expert here).
Issue is that ftl seems quite complicated and seems to add quite some overhead.
(and pardon me if my understanding of ftl is completely off).

Anyway, a good layering would probably be:
optional bad block handling layer
block driver


More information about the linux-mtd mailing list