This message is from the T13 list server.
Hale
I have to disagree with you. I do not have any recollection of read
ahead controlling read cache. To the best of my knowledge, this disables
look ahead in WD drives but has no effect on read cache. Quite frankly I
was shocked to hear that someone was actually interpreting the function as a
cache disable. No ATA rev has even hinted that this was a cache disable...
-------------------------------------------------
Curtis E. Stevens
20511 Lake Forest Drive #C-214D
Lake Forest, California 92630
Phone: 949-672-7933
Cell: 949-307-5050
E-Mail: [EMAIL PROTECTED]
Ambition is a poor excuse for not having enough sense to be lazy.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hale
Landis
Sent: Tuesday, June 28, 2005 10:36 PM
To: [email protected]
Subject: RE: [t13] Read Look Ahead
This message is from the T13 list server.
On Tue, 28 Jun 2005 22:15:51 -0700, Mark Overby wrote:
>This message is from the T13 list server.
>I'm not sure we have consensus on this and I'm not sure that was the
>original intent of that bit.
Actually we are talking about the name of the SET FEATURES
subcommands that has generally been called Enable/Disable Read
Ahead. Probably for the last 10 years the function actually performed
is to enable/disable Read Cache.
>It would appear (based on the discussions at the plenary and side
>discussions I've had with people) that some drives implement this as a
>read cache enable/disable others implement it differently.
I would agree there are many different implementations of Read (and
Write Cache) but I think most people expect the SET FEATURE
subcommands in question to enable/disable the Read (or Write) cache
feature/function in the drive no matter what the actual cache
implementation is.
Hale
*** Hale Landis *** www.ata-atapi.com ***
