From: Andi Kleen <andi@firstfloor.org>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: "Bo Brantén" <bosse@acc.umu.se>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jesse Barnes" <jesse.barnes@intel.com>,
"Andi Kleen" <andi@firstfloor.org>,
linux-kernel@vger.kernel.org
Subject: Re: x86_64 ten times slower than i386
Date: Tue, 6 Nov 2007 01:26:47 +0100 [thread overview]
Message-ID: <20071106002647.GA27182@one.firstfloor.org> (raw)
In-Reply-To: <2c0942db0711050832t5207ea8bib1f75e59e071ade2@mail.gmail.com>
On Mon, Nov 05, 2007 at 08:32:24AM -0800, Ray Lee wrote:
> (Don't trim cc:s.)
>
> On Nov 5, 2007 8:00 AM, Bo Brantén <bosse@acc.umu.se> wrote:
>
> >> Intel Core 2 Quad
> >> and I noticed that the 64-bit versions was at least 10 times slower than the
> >> 32-bit versions,
>
> >
> > After I uppgraded the BIOS the mtrr looks like below, and now it works if
> > I boot with mem=4736M so I can use all memory but it still doesn't work
> > without the mem parameter then it will run as slow as before.
Then the BIOS is still broken Comapl in to your motherboard vendor.
> >
> > reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> > reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> > reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
> > reg03: base=0xcf800000 (3320MB), size= 8MB: uncachable, count=1
> > reg04: base=0xcf700000 (3319MB), size= 1MB: uncachable, count=1
> > reg05: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
> > reg06: base=0x120000000 (4608MB), size= 128MB: write-back, count=1
>
> Jesse Barnes (cc:d) wrote a patch to address this, I think (x86: trim
> memory not covered by WB MTRRs), but as far as I can tell it hasn't
> been merged yet. System is Intel, 4gb of RAM.
It wasn't merged because it broke booting on some systems.
Besides the memory would be still lost -- all it did was to automate
the "mem=XXXX" line.
-Andi
next prev parent reply other threads:[~2007-11-06 0:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 12:31 x86_64 ten times slower than i386 Bo Brantén
2007-11-03 16:26 ` Matt Mackall
2007-11-03 22:38 ` Bo Brantén
2007-11-03 22:54 ` Matt Mackall
2007-11-03 23:30 ` H. Peter Anvin
2007-11-05 8:06 ` Joseph Fannin
2007-11-05 10:15 ` Bo Brantén
2007-11-05 16:00 ` Bo Brantén
2007-11-05 17:23 ` H. Peter Anvin
2007-11-05 18:46 ` Bo Brantén
2007-11-05 19:11 ` H. Peter Anvin
[not found] ` <2c0942db0711050832t5207ea8bib1f75e59e071ade2@mail.gmail.com>
2007-11-06 0:26 ` Andi Kleen [this message]
2007-11-06 1:19 ` H. Peter Anvin
2007-11-06 19:40 ` Willy Tarreau
2007-11-06 19:50 ` H. Peter Anvin
2007-11-06 19:53 ` Willy Tarreau
2007-11-07 18:38 ` Jesse Barnes
2007-11-10 13:41 ` Bo Brantén
2007-11-05 17:22 ` H. Peter Anvin
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=20071106002647.GA27182@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=bosse@acc.umu.se \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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