> I can imagine how it improves sequenial write performace too. With the
> write cache off, the computer cannot send another write request to the IDE
> device until the last one had finished. By the time the computer is told
> the request was finished and it has sent a new request to the drive, the
> disk would have spun out of the place it was supposed to be placed. The
> drive will then have to wait for the disk to spin around fully again
> before doing the write. With the write cache enabled, several requests can
> be placed into the drive buffer and written in the single revolution of
> the drive.
Might be an explanation. How big are the chunks of data that the
kernel sends to the disk?
-- Matthias Andree"Those who give up essential liberties for temporary safety deserve neither liberty nor safety." - Benjamin Franklin - 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/