This message is from the T13 list server.
Mark Overby wrote:
This message is from the T13 list server.
That's interesting Hale, because as a host vendor that's NOT what I
expect to have happen.
If the reality is that some very large % of the drives implement it this
way, then I'd have no problem changing it. But, if it's the other way
around then I'd have a problem changing it because it doesn't reflect
reality.
The other way out of this going forward is to have a seperate bit
indicating if the read cache is completely disabled by this set features
or not.
Are we talking about the same thing?
I am talking about the "name" given to these things:
SET FEATURES subcommands 55H and AAH
- aka disable/enable "read look ahead"
ID word 82 bit 6 and ID word 85 bit 6
- the "read look ahead" supported/enabled bits
The name "read look ahead" is a little out of date. The name "read look
ahead" was introduced 15 years ago before "cache" became a more common
name (back when some drives implemented a very simple read ahead
function and before drives implemented the complex caching see see today).
I think the less confusing name for these would be "read cache" -
especially since "write cache" is used for the corresponding "write
cache" feature.
Hale
--
++ Hale Landis ++ www.ata-atapi.com ++
