From: Jay Strauss <me@heyjay.com>
To: Mike Hardy <mhardy@h3c.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 1 install revealed poor HD performance (I think)
Date: Thu, 19 May 2005 13:40:22 -0500 [thread overview]
Message-ID: <428CDD96.2070006@heyjay.com> (raw)
In-Reply-To: <428CBB4A.8080900@h3c.com>
Mike Hardy wrote:
> That's more like what we were expecting!
>
> I can't tell you why its like that or how, but this *is* the typical
> problem with IDE. Most likely the chipset is being detected incorrectly,
> or its being detected correctly but there is some errata that's
> disabling dma, or maybe dma is experimental for the card.
>
> Places to look for information are in the dmesg for the sis chipset's
> detection diagnostics, then on the internet as a google for your sis
> chipset number then "linux dma" maybe. You may end up with some ide
> things on your kernel command line (via grub or lilo)
>
> I'll reiterate something I said previously though, other than
> write-caching (which is potentially dangerous) none of the other hdparm
> or IDE settings are really going to give you that much of a boost unless
> your workload is specifically tunable. They're all just little minor
> twiddles you can do - nothing even close to the difference between
> having DMA or not. So I'd just focus on enabling DMA. The other stuff is
> all uninteresting compared to it.
>
> -Mike
>
Thanks for the reply Mike. After some Googling and looking at my kernel
config file, it seems that SIS support is a module, like so:
CONFIG_BLK_DEV_SIS5513=m
I found this link but can't find any of the files that it references
http://kerneltrap.org/comment/reply/4925/129324
I'm not sure if having CONFIG_BLK_DEV_SIS5513 as a module has anything
to do with this.
I can't get to my box right now, because out of curiosity I did hdparm
-D 0 /dev/hda and ran the dd test, I think it crashed the box. The box
is in my basement at home, so I'll have to wait until tonight.
Jay
next prev parent reply other threads:[~2005-05-19 18:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 15:11 Raid 1 install revealed poor HD performance (I think) Jay Strauss
2005-05-17 15:50 ` Gordon Henderson
2005-05-17 16:17 ` Jay Strauss
2005-05-17 16:23 ` Gordon Henderson
2005-05-17 16:52 ` Mike Hardy
2005-05-17 20:51 ` Jay Strauss
2005-05-17 20:54 ` Mike Hardy
2005-05-17 22:16 ` Tobias Hofmann
2005-05-17 23:00 ` Jay Strauss
2005-05-18 3:28 ` Jay Strauss
2005-05-17 22:45 ` Peter T. Breuer
2005-05-17 23:42 ` Henrik Holst
2005-05-18 3:30 ` Jay Strauss
2005-05-17 23:44 ` Henrik Holst
2005-05-19 15:32 ` Jay Strauss
2005-05-19 16:14 ` Mike Hardy
2005-05-19 18:40 ` Jay Strauss [this message]
2005-05-19 20:43 ` Mike Hardy
2005-05-20 1:43 ` Jay Strauss
[not found] <Pine.LNX.4.44.0505180206580.1777-100000@coffee.psychology.mcmaster.ca>
2005-05-18 15:08 ` Mike Hardy
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=428CDD96.2070006@heyjay.com \
--to=me@heyjay.com \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.com \
/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;
as well as URLs for NNTP newsgroup(s).