From: Christer Weinigel <christer@weinigel.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MediaGX/Geode performance fix, Was: Which processor/board for embedded NTP
Date: 20 Sep 2002 11:59:42 +0200 [thread overview]
Message-ID: <87fzw5t20h.fsf@zoo.weinigel.se> (raw)
In-Reply-To: <1032477107.29021.4.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Thu, 2002-09-19 at 20:39, Christer Weinigel wrote:
> > This mail contains a patch to fix a performance problem with many
> > Cyrix MediaGX/NatSemi Geode platforms. The register settings have
> > been officially recommended by NatSemi themselves. The patch is
> > against linux-2.4.20-pre7. Should this be merged into the mainsteam
> > linux kernel?
>
> This wont actually make an iota of difference in most cases. The CS5530
> IDE driver will force this value to 0x14 anyway. It also sets MWI on te
> X-bus which is needed too.
Ok, it did make a 5% difference when I did some quick tests on TCP
performance. But I didn't have the CS5530 IDE driver loaded.
> Probably the fixup should be done in the PCI quirks.
Sounds it should be moved from the IDE driver to quirks at least, but
that might be a 2.5 thing in that case.
/Christer
--
"Just how much can I get away with and still go to heaven?"
Freelance consultant specializing in device driver programming for Linux
Christer Weinigel <christer@weinigel.se> http://www.weinigel.se
prev parent reply other threads:[~2002-09-20 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 13:10 Which processor/board for embedded NTP Olaf Frączyk
2002-09-18 13:58 ` Alan Cox
2002-09-18 14:24 ` Athlon/via problems continued Kirk Reiser
2002-09-18 19:37 ` Which processor/board for embedded NTP Christer Weinigel
2002-09-19 6:02 ` Robert Schwebel
2002-09-19 19:39 ` MediaGX/Geode performance fix, Was: " Christer Weinigel
2002-09-19 23:11 ` Alan Cox
2002-09-20 9:59 ` Christer Weinigel [this message]
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=87fzw5t20h.fsf@zoo.weinigel.se \
--to=christer@weinigel.se \
--cc=alan@lxorguk.ukuu.org.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