From: Erik Andersen <andersen@codepoet.org>
To: Davidovac Zoran <zdavid@unicef.org.yu>
Cc: Torrey Hoffman <torrey.hoffman@myrio.com>,
"'Matthias Schniedermeyer'" <ms@citd.de>,
Rik van Riel <riel@conectiva.com.br>,
Ben Israel <ben@genesis-one.com>,
linux-kernel@vger.kernel.org
Subject: Re: Disk Performance
Date: Sat, 10 Nov 2001 10:51:38 -0700 [thread overview]
Message-ID: <20011110105138.A11060@codepoet.org> (raw)
In-Reply-To: <D52B19A7284D32459CF20D579C4B0C0211CABE@mail0.myrio.com> <Pine.LNX.4.33.0111101746020.11836-100000@unicef.org.yu>
In-Reply-To: <Pine.LNX.4.33.0111101746020.11836-100000@unicef.org.yu>
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--
next prev parent reply other threads:[~2001-11-10 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 1:21 Disk Performance Torrey Hoffman
2001-11-10 16:47 ` Davidovac Zoran
2001-11-10 17:51 ` Erik Andersen [this message]
[not found] <fa.jmrptbv.1dh8ur1@ifi.uio.no>
2001-11-10 8:03 ` Dan Maas
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 21:04 Ben Israel
2001-11-09 22:31 ` Rik van Riel
2001-11-09 22:53 ` Erik Andersen
2001-11-09 22:57 ` Rik van Riel
2001-11-09 23:20 ` Erik Andersen
2001-11-09 23:45 ` Matthias Schniedermeyer
2001-11-11 19:24 ` Maxwell Spangler
2001-11-11 21:52 ` Andre Hedrick
2001-11-11 20:56 ` Maxwell Spangler
2001-11-11 22:17 ` Andre Hedrick
2001-11-12 6:02 ` Erik Andersen
2001-11-09 23:24 ` Alan Cox
2001-11-09 22:35 ` Doug McNaught
2001-11-09 23:33 ` Stefan Smietanowski
2001-11-09 23:50 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011110105138.A11060@codepoet.org \
--to=andersen@codepoet.org \
--cc=ben@genesis-one.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
--cc=riel@conectiva.com.br \
--cc=torrey.hoffman@myrio.com \
--cc=zdavid@unicef.org.yu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox