IMPROVING APPLICATION RESPONSE TIMES OF NAND FLASH…….ppt

FSAF – File System Aware FTL FSAF: Monitors write requests to FAT32 table to interpret any deleted data dynamically, Optimizes GC and WL algorithms to treat dead data Carries out proactive reclamation to handle large dead data content Interpreting Flash Formatting Format - the structure of file system data structure residing on Flash FSAF interprets Format and keeps track of changes to the Master Boot Record (MBR) and the first sector in the file system called FAT32 Volume ID. The location of FAT32 table: : The size of the FAT32 table FAT32 Table Dead Data Detection Calculate size and location of FAT32 Table by reading MBR and FAT32 Volume ID sectors Monitor writes to FAT32 Table If a sector pointer is being zeroed out, mark corresponding sector as dead Mark a block as dead if all the sectors in the block are dead Dead Data Reclamation Avoidance of Dead Data Migration: Dead data is marked NOT to be copied during GC and WL Proactive Reclamation: Large deleted files occupy complete blocks – no copying costs to reclaim these! Experiments Used trace-driven approach Benchmarks: From several media applications and file scenarios (MP3, MPEG, JPEG, etc) Initialized flash to 80% utilization GC starts when #free blocks falls below 10% of total blocks and stops as soon as percent free blocks reaches 20% of total blocks. WL is triggered whenever the difference between maximum and minimum erase counts of blocks exceeds 15. The size of files used in various scenarios was varied between 32MB to 2KB. Configuring FSAF Parameters δ - dead content threshold μ - system utilization threshold Δ – threshold that determines #dead block reclamations To set δ and μ: Ran proactive reclamation with various values of δ and μ Results – Higher values lead to higher efficiency By setting these to high as possible, proactive reclamation is triggered only when the system is low in free space, but runs frequently enough to generate sufficient free space. To set Δ: observed