dimag0g
Very Active Member
OK, so the controller may identify the clusters occupied by the file that is being read/written, so that it can guess ahead provided that the file is accessed sequentially. Why not skip this stage and optimize for contiguous reads/writes, given that FAT (and any other filesystem for that matter) makes an effort to allocate files contiguously?Their way of file allocation and indexing works entirely different, though. The simple structure of FAT based filesystem surely offers some potential to make educated guesstimations on how things are being written. For example, the FTL could directly analyze the FAT itself - imagine a really crappy FTL that expects the FAT at a fixed position and only finds garbage because the drive was formatted with ext3.
Last edited by a moderator: