On Wed, 7 Mar 2001, Jonathan Morton wrote:
> Still doesn't make a difference - there is one revolution between writes,
> no matter where on disk it is.
Oh it does, because you are hitting the same sector with the same data.
Rotate your buffer and then you will see the difference.
> >Because of WinBench!
> >All the prefetch/caching are modeled to be optimized to that bench-mark.
>
> Lies, damn lies, statistics, benchmarks, delivery dates. Especially a
> consumer-oriented benchmark like WinBench. It's perfectly natural to
> optimise for particular access patterns, but IMHO that doesn't excuse
> breaking the drive just to get a better benchmark score.
Obviously you have never been in the bowls of drive industry hell.
Why do you think there was a change the ATA-6 to require the
Write-Verify-Read to always return stuff from the platter?
Because the SOB's in storage LIE! A real wake-up call for you is that
everything about the world of storage is a big-fat-whopper of a LIE.
Storage devices are BLACK-BOXES with the standards/rules to communicate
being dictated by the device not the host. Storage devices are no beter
then a Coke(tm) vending machine. You push "Coke" it gives you "Coke".
You have not a clue to how it arrives or where it came from.
Same thing about reading from a drive.
> That isn't the point! I'm not talking about the physical mechanism, which
> indeed is often the same between one generation of SCSI and the next
> generation of IDE devices. I'm talking about the IDE controller which is
> slapped on the bottom of said mechanism. The mech can be of world-class
> quality, but if the controller is shot it doesn't cut the grain.
So there is a $5 differnce in the cell-gates and the line drivers are more
powerful, 80GB ATA + $5 != 80GB SCSI.
> >Since all OSes that enable WC at init will flush
> >it at shutdown and do a periodic purge with in-activity.
>
> But Linux doesn't, as has been pointed out earlier. We need to fix Linux.
Friend I have fixed this some time ago but it is bundled with TASKFILE
that is not going to arrive until 2.5. Because I need a way to execute
this and hold the driver until it is complete, regardless of the shutdown
method.
> >Err, last time I check all good devices flush their write caching on their
> >own to take advantage of having a maximum cache for prefetching.
>
> Which doesn't work if the buffer is filled up by the OS 0.5 seconds before
> the power goes.
Maybe that is why there is a vender disk-cache dump zone on the edge of
the platters...just maybe you need to buy your drives from somebody that
does this and has a predictive sector stretcher as the energy from the
inertia by the DC three-phase motor executes the dump.
Ever wondered why modern drives have open collectors on the databuss?
Maybe to disconnect the power draw so that the motor now generator
provides the needed power to complete the data dump...
> I'm sorry if this looks like another troll, but I really do like to clear
> up confusion. I do accept that IDE now has good enough real performance
> for many purposes, but in terms of enforced quality it clearly lags behind
> the entire SCSI field.
I have no desire to debate the merits, but when your onboard host for ATA
starts shipping with GigaBit-Copper speeds then we can have a pissing
contest.
Cheers,
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035 Web: www.aslab.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:22 EST