From: TimO <hairballmt@mcn.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Only 10 MB/sec with via 82c686b chipset?
Date: Wed, 21 Mar 2001 19:14:04 -0700 [thread overview]
Message-ID: <3AB95FEC.6D27CB24@mcn.net> (raw)
In-Reply-To: <20010321143956.917977A94@Nicole.muc.suse.de>
egger@suse.de wrote:
>
> On 20 Mar, SodaPop wrote:
>
> > I have an IWill KK-266R motherboard with an athlon-c 1200
> > processor in it, and for the life of me I can't get more than
> > 10 MB/sec through the on-board ide controller. Yes, all the
> > appropriate support is turned on in the kernel to enable dma
> > and specific chipset support, and yes, I think I have all
> > relevant patches and a reasonable kernel.
>
> Yes, actually I'm seeing the same on a KT133 board from Elitegroup.
> Although here I get a bit more: 15 MB/s
>
> > I noted a number of other interesting things; one, that -X33,
> > -X34, and -X64 through -X69 all have the same 10 MB/sec transfer
> > rate, and two, that the 10 MB/sec transfer rate can be linearly
> > increased to 12 MB/sec by raising the system bus from 100 mhz to
> > 120 mhz (all components are safely rated at 133, no overclocking
> > involved.)
>
> Duh, before making such a claim you should consider the fact that
> this is overclocking your PCI/AGP bus and I have yet to see any
> graphic cards/IDE controllers/other devices which are rated for
> 37MHz PCI bus speed.
>
> --
>
> Servus,
> Daniel
Actually this depends on the MB. On mine for instance (Athlon also, but
not IWill), the PCI bus is a quotient of the oscillator and the FSB is
a multiple of the PCI and the CPU & ev6 are multiples of the FSB.
Memory
speed is also a multibple of PCI. In this case increasing the FSB
doesn't increase the PCI. Mine has two crystals 100/133 jumper con-
figurable.
Anyway this is probably getting way off-topic; although I'd kinda like
to see Dennis' output of both buffered and sustained output. Looks
kinda
like a hw config problem. Mine for comparison:
Maxtor 13.4 Gig 5400rpm ATA66
Buffered: ~170 - 175 MB
Sustained: ~24 MB inner ~26 MB outer
PCI: 33 FSB: 100 Memory 128M@133 CPU: 750Mhz EV6: 200
===============
-- Tim
--------------------==============++==============--------------------
next prev parent reply other threads:[~2001-03-22 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 3:48 Only 10 MB/sec with via 82c686b chipset? SodaPop
2001-03-21 13:48 ` egger
2001-03-22 2:14 ` TimO [this message]
2001-03-23 2:38 ` Only 10 MB/sec with via 82c686b - FIXED SodaPop
2001-03-23 9:48 ` Alan Cox
2001-03-23 16:21 ` SodaPop
2001-03-23 17:00 ` [PATCH] Prevent OOM from killing init SodaPop
2001-03-23 18:42 ` Martin Dalecki
2001-03-23 20:25 ` SodaPop
2001-03-23 20:33 ` Martin Dalecki
2001-03-23 19:19 ` Jonathan Morton
2001-03-23 2:59 ` Only 10 MB/sec with via 82c686b - FIXED SodaPop
2001-03-21 14:18 ` Only 10 MB/sec with via 82c686b chipset? Jonathan Morton
2001-03-21 17:34 ` egger
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=3AB95FEC.6D27CB24@mcn.net \
--to=hairballmt@mcn.net \
--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