File system support on Multi Level Cell (MLC) flash in open source.pptVIP

File system support on Multi Level Cell (MLC) flash in open source April 17, 2008 Kyungmin Park Software Laboratories Samsung Electronics Contents Introduction Multi Level Chip (MLC) Current status Known Issues Patents Consideration in JFFS2 Summary References Introduction It’s not cover Flash properties Write/read disturb Hardware issues Controller embedded It’s talking about the MLC software itself How to use MLC flash directly? What’s the consideration on MLC? Multi Level Cell (MLC) Capable for low-cost consumer applications Media players, MP3 devices, media cards, and USB flash drives Gray code is dependent on each manufacturers Multi Level Cell (MLC) I/O split vs. Page split Performance Endurance Wear-leveling Current status Why there’s no software using MLC directly in linux? JFFS2 doesn’t support the MLC YAFFS MLC NAND handling is under way UBIFS??? LogFS??? Another approaches Embedded MMC (eMMC) Controller embedded Samsung MoviNAND, Micron ManagedNAND Solid State Drive (SSD) Etc. What’s the issues? Known Issues Number Of Program (NOP) 1 Write the page only once It’s simple and already done. Spare Area MLC uses the more powerful ECC/EDC mechanism It means it requires the more spare area Handle the paired page problem A lot of solutions but patents NOP 1 JFFS2 uses the NOP 2 main area and OOB area for cleanmarker UBI uses MAX NOP 4 by the provided subpage_sft E.g., subpage_sft = 2 Sector write (4) Add the MTD_OOB_WRITEABLE bit Clearing the MTD_OOB_WRITEABLE bit if the probed chip is MLC. Assign the subpage_sft to 0 Disable the subpage write Spare Area Spare usages are dependent on each filesystems In worse case it can’t use the spare area Paired Page Problem The pages are coupled in MLC. When program operation is abnormally aborted (ex. power-down, reset), not only page data under program but also paired page data may be damaged even though it was written correctly at previous time It’s dependent on each manufacturers. E.g., Th