Messages in this thread | | | Date | Sat, 10 Nov 2001 10:51:38 -0700 | From | Erik Andersen <> | Subject | Re: Disk Performance |
| |
On Sat Nov 10, 2001 at 05:47:15PM +0100, Davidovac Zoran wrote: > try > hdparm -d1 /dev/hda > hdparm -d1 /dev/hdb > and test them now
Sure. But that isn't the point. The point is that even if the drive is capable and the chipset is capable, there still seem to be corner cases where DMA is not enabled.
In my case, the chipset and drives in my box are both known to work with DMA enabled and the ide chipset is even in the IDEDMA white list. But DMA is still not being enabled by default, so there is a bug somewhere,
So why don't I want to hard code hdparm in an init script? Lets suppose for a moment there are programs that need to run on all sorts of strange hardware and which depend on trying to run the hard drives as fast as possible. For example, think of the installer for your favorite distro. Redhat or Debian or whatever couldn't very well put 'hdparm -d1 /dev/hda' in the init scipts since for all they know there might be a cmd640 under the hood...
-Erik
-- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- - 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/
| |