From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
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: Thu, 03 Mar 2005 12:02:10 +0000 [thread overview]
Message-ID: <1109851329.21781.41.camel@localhost.localdomain> (raw)
In-Reply-To: <20050302222826.GS1512@redhat.com>
On Mer, 2005-03-02 at 22:28, Dave Jones wrote:
> 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.
Yep - providing your kernel is built for it you get about 20-30% speed
up against a base kernel. It's the one freak case (in 2.4 anyway) where
kernel cpu options matter.
Alan
next prev parent reply other threads:[~2005-03-03 12:09 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
2005-03-03 12:02 ` Alan Cox [this message]
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=1109851329.21781.41.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--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