On Thu, Jan 15, 2009 at 8:06 AM, James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: ... > Right, this is the flash cache idea that's been floating around for a > while. It's even been suggested as a way of avoiding the IDE barrier > flush penalties. I think Seagate went as far as making hybrid drives > that were a large flash cache backed by rotational storage. "inline" RAM caches were implemented 10+ years ago for SCSI devices to avoid seek *and* rotational delay penalties. These were transperent SCSI devices that would cache and prefetch content from disks. For the given dataset size, the seek cost was effectively zero. This is mostly true today for high-end disk arrays which have large RAM front-end's (TB) and very smart data placement strategies (reduced seek). Back to the bikeshed painting: I prefer two flags: "AVGREADCOST" and "AVGWRITECOST as the flag. This isn't just about seek. Rotational delay @7200 RPM is 8.3ms. Making both non-zero implies rotational media. Different devices have different read and write characteristics. Flash typically has a much higher write cost than read cost. Disks (because of WCE) can be the opposite. Code can test for zero/nonzero or (preferably) more fine grained. e.g. "avgreadcost > 1ms" or "avgwritecost". I'm hoping this test can be abstracted into a macro. I'm hoping longterm, the values could be "self tuning" but don't know how that might work - e.g. 1 minute avg? 10 minute avg? Cost of collecting/maintaining the stats? Feels like a CONFIG option. hth, grant -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
