From: Dave Jones <davej@redhat.com>
To: Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
torvalds@osdl.org, akpm@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remove dead cyrix/centaur mtrr init code
Date: Wed, 2 Mar 2005 17:28:26 -0500 [thread overview]
Message-ID: <20050302222826.GS1512@redhat.com> (raw)
In-Reply-To: <20050302222106.GI20190@apps.cwi.nl>
On Wed, Mar 02, 2005 at 11:21:06PM +0100, Andries Brouwer wrote:
> On Wed, Mar 02, 2005 at 01:45:43PM +0000, Alan Cox wrote:
> > On Mer, 2005-03-02 at 08:02, Dave Jones wrote:
> > > If there are any of them still being used out there, I'd be even
> > > more surprised if they're running 2.6. Then again, there are
> > > probably loonies out there running it on 386/486's. 8-)
> >
> > I have one here running 2.4 still. I can test a 2.6 fix for the mtrr
> > init happily enough.
>
> Good. If I understand things correctly - you or davej or someone will
> correct me otherwise - failing to initialise mtrr does not break anything,
> it would just mean slower access to certain kinds of memory for certain
> kinds of access patterns. (Would you test using an X benchmark?)
The winchips had a funky feature where you could mark system ram
writes as out-of-order. This led to something like a 25% speedup iirc
on benchmarks that did lots of memory copying. lmbench showed
significant wins iirc, but any results I had saved are long since
wiped out in hard disk failures/cruft removal over the years.
> Below roughly speaking the same patch as before, but with calls
> to the cyrix and centaur mtrr init routines inserted.
Looks ok on a quick eyeball.
Dave
next prev parent reply other threads:[~2005-03-02 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 19:20 [PATCH] remove dead cyrix/centaur mtrr init code Andries Brouwer
2005-02-28 19:35 ` Adrian Bunk
2005-02-28 21:51 ` Andries Brouwer
2005-03-01 23:52 ` Alan Cox
2005-03-02 7:50 ` Andries Brouwer
2005-03-02 8:02 ` Dave Jones
2005-03-02 13:45 ` Alan Cox
2005-03-02 22:21 ` Andries Brouwer
2005-03-02 22:28 ` Dave Jones [this message]
2005-03-03 12:02 ` Alan Cox
2005-03-02 19:14 ` Nuno Monteiro
2005-03-02 14:59 ` Ondrej Zary
2005-03-02 19:18 ` Dave Jones
2005-03-02 21:30 ` Ondrej Zary
[not found] <200503081937.j28Jb4Vd020597@hera.kernel.org>
2005-03-09 16:55 ` Alan Cox
2005-03-09 17:09 ` Linus Torvalds
2005-03-09 18:23 ` Alan Cox
2005-03-09 19:09 ` Andries Brouwer
2005-03-09 20:36 ` Alan Cox
2005-03-14 17:38 ` Alan Cox
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=20050302222826.GS1512@redhat.com \
--to=davej@redhat.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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