From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: James Finnie <jf1@IMERGE.co.uk>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: VIA IDE performance under 2.6.0-test7/8?
Date: Tue, 21 Oct 2003 19:40:44 +0100 [thread overview]
Message-ID: <3F957DAC.6080901@superbug.demon.co.uk> (raw)
In-Reply-To: <C0D45ABB3F45D5118BBC00508BC292DB016038F5@imgserv04>
James Finnie wrote:
> Hi guys;
>
> Am having trouble getting decent IDE performance from the 2.6.0-test8 kernel
> (tested with 2.6.0-test7 kernel also, same issue). The platform is VIA
> EPIA-ME6000 - with a VIA VT8235 southbridge. Under 2.4.21 I get around
> 40Mb/s in hdparm -t and 70Mb/s for hdparm -T. Under the 2.6.0-test7/8 I
> only manage 13Mb/s & 52Mb/s respectively! I've attached my .config, and the
> output of /proc/ide/via, dmesg, and hdparm info. I don't think I'm doing
> anything particularly stupid here, but if I am, hit me with a wet fish
> please :)
>
> Thanks for all help,
>
> James
>
Can you also send the output from "cat /proc/interrupts".
It looks like you are not using IO-APIC, but instead using XT-PIC.
XT-PIC is a lot slower than IO-APIC.
Just turn on SMB support in the "make menuconf", and it should enable
IO-APIC.
If you cannot boot using IO-APIC, you probably have one of the bad VIA
motherboards. I have not determined if the IO-APIC issues with VIA
VT8235 MBs is hardware or software related. All I know, is some VIA
VT8235 MBs work, and some don't. I am still investigating why.
Cheers
James
next prev parent reply other threads:[~2003-10-21 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 14:37 James Finnie
2003-10-21 14:55 ` Bartlomiej Zolnierkiewicz
2003-10-21 18:40 ` James Courtier-Dutton [this message]
2003-10-22 11:27 ` Knut Petersen
2003-10-22 12:34 ` Knut Petersen
2003-10-21 15:11 James Finnie
2003-10-22 11:11 James Finnie
2003-10-22 12:31 James Finnie
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=3F957DAC.6080901@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=jf1@IMERGE.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome