| |||||||||||||
Supporting block I/O contextsSupporting block I/O contextsPosted Jun 21, 2012 10:38 UTC (Thu) by etienne (subscriber, #25256)Parent article: Supporting block I/O contexts
At the minimum, the context should change when writing data or metadata or journal - would be nice for FAT at least, if possible the default for all filesystems.
(Log in to post comments)
Supporting block I/O contexts Posted Jun 22, 2012 9:11 UTC (Fri) by arnd (subscriber, #8866) [Link]
We already have the "data tag" support, which is used to annotate metadata. In eMMC 4.5 any request can be tagged either metadata or belonging to one of 5 to 15 contexts, or being unspecified. Any request that a file system flags as a REQ_META write uses the data tag.
Since FAT is both very simple and very common, a lot of the flash devices actually have logic in them to detect the access patterns even without those annotations. Usually the FAT area is known to be at the beginning of the device (partition-less SD cards and older USB sticks) or an erase block that receives lots of random I/O is expected to be the FAT. Further, devices often expect a FAT cluster size of 32KB, so all requests of that size are taken to be data while all smaller ones are treated as directory updates.
|
|||||||||||||