| |||||||||||||
JFFS2, UBIFS, and the growth of flash storageJFFS2, UBIFS, and the growth of flash storagePosted Dec 13, 2012 18:39 UTC (Thu) by yoush (subscriber, #38940)Parent article: JFFS2, UBIFS, and the growth of flash storage
When running ubi over block2mtd over FTLed flash, FTL in flash still operates, and affects both performance and reliability (i.e. wear-leveling).
UBI guaranteed wear-leveling is effectively turned into random thing.
FTLs are known to start badly misbehave after some time if they don't get information about which blocks are free. So unless TRIM commands are used, "ubi over block2mtd over FTLed flash" will badly degrade in time.
Getting raw access to flash devices (bypassing vendor FTLs) is indeed the best possible scenario, because this gives way to open development of reliable and high-performance algorithms to manage those.
(Log in to post comments)
JFFS2, UBIFS, and the growth of flash storage Posted Dec 15, 2012 23:26 UTC (Sat) by marcH (subscriber, #57642) [Link]
> Getting raw access to flash devices (bypassing vendor FTLs) is indeed the best possible scenario, because this gives way to open development of reliable and high-performance algorithms to manage those.
With current flash technologies and their rate of progress this would practically require writing one different driver per flash chip.
Maybe what's required is something in the middle: some kind of new, more evolved standard interface, something block+page based?
Anyone having worked on MTD should know.
|
|||||||||||||