Re: Lifetime of flash memory

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Sun, Mar 26, 2006 at 08:36:48PM +0400, Artem B. Bityutskiy wrote:
> I'm actually interested in:
> 
> 1. CF wear-levelling algorithms: how good or bad is it?

Depends on the maker.

> 2. How does CF implement block mapping, does it store the mapping table 
> on-flash or in memory, does it build it by scanning, how scalable are 
> those algorithms.

Well the map has to be stored in flash or other non volatile memory.

> 3. Does CF perform bad erasable blocks hadling transparently when new 
> bad eraseblocks appear.

No idea, but it is almost certainly also vendor specific.

> 4. How tolerant CF to powrer-offs.

I have seen some that a power off in the middle of a write would leave
the card dead (it left it with a partially updated block map).  On
others nothing happened (well you loose the write in progress of course
just as a harddisk would).

> 5. Is there a Garbage Collector in CF and how clever/stupid is it.

That is vendor specific.  Depends how they did it.  Different
generations from a given company may also be different in behaviour.  I
imagine some parts of it are patented by some of the comapnies involed
in flash card making.

> I've heard CF does not have good characteristics in the above mentioned 
> aspects, but still, it would be interesting to know details. I'm not 
> going to use CFs, but as I'm working with flashes, I'm just interested. 
> It'd help me explaining people why it is bad to use CF for more serious 
> applications then those just storing pictures.

The wearleveling is not a part of the CF spec.  So saying anything about
CF in general just doesn't make much sense.  It all depends on the
controller in the CF you are using.

Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/