Re: [PATCH] 2.5.6 IDE 19

Bill Davidsen
2002-03-12T00:50:10Z

On Mon, 11 Mar 2002, Martin Dalecki wrote:

> Alan Cox wrote:

> > Oh dear me. Wrong again. Microdrives require proper polite wakeups. But you
> > see camera vendors buy in IDE code from people who can read and follow
> > standards documents.

This seems relevant in light of:

[snip]

> Fsck let's cite the IBM appilcation notes about the Micro Drive
> found here http://www.storage.ibm.com/hdd/micro/appguide.htm

[snip, but relevant]

> * Consideration for a time-out value when using the write cache
>
> The microdrive can queue several consecutive write commands. Even if the host
> system receives a
> command completion, the microdrive may still be performing disk writing for
> queued commands, each of
> which could take up to 7.5 seconds as previously mentioned if an error has
> occurred and an error
> recovery routine starts.
> This delay eventually surfaces when processing a first non-queued command during
> write cache.
>
> For example, suppose the microdrive queues 2 write commands and each command
> takes 7.5 seconds
> for some extreme reason. Then if the microdrive receives Read Sectors, which is
> a non-queue command,
> it will be processed just after disk writing is completed. In the worst case,
> delay for the Read Sectors
> would be close to 15 seconds (7.5 x 2).
>
> In light of the stuation above, IBM recommends 30 seconds as a time-out value
> if the host system uses
> the write cache feature.
>
>
> And apparently we see that there is nothing special about them... Just don't
> enable the write cache and all should be well with a timeout of 30 seconds.

How can you read that recommendation into what you just quoted? IBM says
use 30 sec if you enable write buffers, why would eliminate the long delay
but use the slow timeout anyway? To slow retry to a crawl? It would seem
obvious to do one thing or the other, but not to take all possible action
to make things crawl. I suggest that the obvious solution is use a
sensible timeout without write buffers to be really safe, or to get best
performance use the write buffers and force a flush at a sensible point,
somewhat like flushing buffers to disk with bdflush. There are already
spindown timers and such in the drivers, this isn't a "whole new thing."

Since we have the ability to let the user set this now, I see no reason
not to let the user make the choice, Linux is about choice.

Finally, about copying other drivers: to quote my youngest, "yuckie-poo!"
Drivers should be written to the standard, with reality dictating that it
is sometimes required to write to the hardware when you absolutely MUST
use non-compliant hardware. To copy code from another driver seems like a
lack or either ability or committment.

--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.