| |||||||||||
FLASH drives do need a scheduler policyFLASH drives do need a scheduler policyPosted Oct 1, 2004 6:29 UTC (Fri) by axboe (subscriber, #904)In reply to: FLASH drives do need a scheduler policy by dmaxwell Parent article: Modular, switchable I/O schedulers
It still doesn't change the fact that you cannot solve this problem at the block layer, as you don't have enough information to do so - all you get is a start offset and length of where to write the data. If you get writes for the same blocks every few seconds, you must look elsewhere to fix it.
And FAT32 is fine to use on a flash stick.
(Log in to post comments)
FLASH drives do need a scheduler policy Posted Oct 1, 2004 16:51 UTC (Fri) by BrucePerens (subscriber, #2510) [Link] Jens,Yes, that's true. However, it can be fixed, if the filesystem communicates either a write barrier (write this block before any blocks I send down after it) or ordering information (write block X before block Y, order of block Z doesn't matter). Once it is so easy to work on I/O scheduling, the need for this will become so evident that there is no question that it will be done. Bruce
FLASH drives do need a scheduler policy Posted Oct 3, 2004 9:48 UTC (Sun) by axboe (subscriber, #904) [Link] Bruce,
We already have write barriers, and it doesn't solve the entire problem. It will make any given fs more flash friendly indeed, but it's still quite a bit away from a fs specifically designed to minimize drive wear.
Your last sentence doesn't make sense.
Jens
FLASH drives do need a scheduler policy Posted Oct 3, 2004 12:06 UTC (Sun) by BrucePerens (subscriber, #2510) [Link] Jens,OK. I think one of the BSDs goes a bit further than write barriers in communicating time information. But I see your point that this can not go all of the way in reducing FLASH wear. Thanks Bruce
|
|||||||||||