From: James Morris <jmorris@intercode.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance issue in 2.5.32+
Date: Tue, 10 Sep 2002 02:06:04 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0209100150490.25061-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0209081055310.14734-100000@home.transmeta.com>
On Sun, 8 Sep 2002, Linus Torvalds wrote:
> I don't really see anythign very suspicious in the 31->32 changelogs.
> Somebody else already mentioned TLS etc, but that shouldn't really be
> noticeable...
I've now tracked the problem to the introduction of the new mtrr code, and
backing it out for 2.5.32 restores original performance. From what I can
tell, the new code is not handling a bios/hardware bug that the old code
was.
The old mtrr code says this during bootup:
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: your CPUs had inconsistent variable MTRR settings
mtrr: probably your BIOS does not setup all CPUs
While the new code just says:
mtrr: SMP support incomplete for this vendor
The peformance hit is basically the same as when the old mtrr code is
disabled. I'll have a poke around and see if I can find out why the new
mtrr code isn't handling the problem.
- James
--
James Morris
<jmorris@intercode.com.au>
next prev parent reply other threads:[~2002-09-09 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 11:46 James Morris
2002-09-08 11:57 ` Andi Kleen
2002-09-08 12:55 ` James Morris
2002-09-08 15:45 ` Linus Torvalds
2002-09-08 17:40 ` James Morris
2002-09-08 18:09 ` Linus Torvalds
2002-09-09 16:06 ` James Morris [this message]
2002-09-08 13:19 rwhron
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=Mutt.LNX.4.44.0209100150490.25061-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®