On Fri, 2003-02-21 at 13:08, Hicks, Jamey wrote:
> Thinking about this a little more, one could implement wear-leveling
> in the fat filesystem implementation. It wouldn't be perfect, but it
> would be pretty good. For file contents, it would be pretty easy:
> just allocate blocks fifo-fashion, and all new or updated files get
> written to the least-recently-used flash blocks. For directories,
> it's not as good, but I think it could mark any changed entries as
> unused and then append the new value of the entries. Every once in a
> while it would coallesce all the entries in a directory. The root
> directory is in a fixed place -- that would be the worst part. I
> guess it could allocate a fairly large amount of space for it and
> handle the blocks there in LRU fashion as well and extend the life of
> the card while having it be interoperable with windows.
The FAT(s) would be the worst part, and you can't work around that as
easily as you can the root directory simply by ensuring you always
create and use subdirs.
> Of course, if you don't need to interoperate with windows then jffs2
> or yaffs would be the way to go.
Bah. Just port to Windows :)
-- dwmw2Received on Fri Feb 21 13:27:55 2003
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:45:01 EDT