I don't think the whole notion of such algorithm is applicable to the flash devices at all.
"Removable flash memory cards and USB flash drives have built-in controllers to perform wear leveling and error correction so use of a specific flash file system does not add any benefit.", according to this:
http://en.wikipedia.org/wiki/Flash_memory#Flash_file_systems[^].The algorithms like SCAN are
elevator algorithms, a kind of
disk scheduling responsible for mechanical arm/head motion scheduling,
http://en.wikipedia.org/wiki/Elevator_algorithm[
^],
http://en.wikipedia.org/wiki/I/O_scheduling[
^].
As flash units come with built-in controllers and their own SRAM buffers (for serial flash, according to
http://en.wikipedia.org/wiki/Flash_memory[
^]), there is no need for a common interface at the level of disk scheduling, hence there is no a need for a functional code unit homological to a hard drive elevator algorithms or disk scheduling algorithms in general. All such HD-related algorithms are based on the fact of considerable seek latency. In flash memory, even if the physical access to the flash is somewhat slower then the access to the SRAM buffer or, say, DRAM, so the caching techniques are still actual, the seek time issues are not.
—SA
Submit an article or tip