Linked by Thom Holwerda on Thu 6th Nov 2008 15:33 UTC, submitted by Gregory
Permalink for comment 336583
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2005-09-01
I guess this is exactly what UBIFS (and I guess Extreme FFS too) is supposed to do: treat whole FLASH as a huge log file registering all write operations and run garbage collection in some backroung thread to reclaim outdated entries. The block map resides in ram, is written to flash device on umount time but can always be rebuilt from the scattered logs (which contain enough metadata aside from content) in case of power failure.
This fully embraces FLASH performance specifics:
Slow inplace write + 0 seek time.