public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: no more MTRRs available ?
Date: Wed, 29 Jan 2003 18:12:15 +0000	[thread overview]
Message-ID: <20030129181215.GF1856@codemonkey.org.uk> (raw)
In-Reply-To: <20030129180011.GN780@holomorphy.com>

On Wed, Jan 29, 2003 at 10:00:11AM -0800, William Lee Irwin III wrote:

 > >> reg00: base=0xc0000000 (49152MB), size=16384MB: uncachable, count=1
 > >> reg01: base=0x00000000 (   0MB), size=524288MB: write-back, count=1
 > >> reg02: base=0x800000000 (524288MB), size=262144MB: write-back, count=1
 > >> Yes, this is standard ia32 (P-III/Coppermine cpus), and hence the
 > >> numbers here are utter garbage.
 > 
 > On Wed, Jan 29, 2003 at 05:48:42PM +0000, Dave Jones wrote:
 > > Bizarre. The size field isn't being shifted, and your base is somewhere
 > > off in 64bit land.
 > > See Andi's "RED-PEN" comments in various parts of arch/i386/kernel/cpu/mtrr/
 > > They need fixing at some point, and could be the cause of your problems.
 > 
 > OTOH since 0-512GB are in there this explains why the (massive) perf.
 > decrease only happens sometimes. The MTRR corruption issues are only
 > visible with 48GB atm. I haven't been focusing on MTRR's but I may
 > arrange to trace the codepaths etc. in the eventual future to find
 > where the bits are going bad esp. as benchmark time approaches.

ohhh, 48GB. I forgot you were doing the silly-amounts-of-mem thing.
Its extremely likely you'll have to fix up those comments Andi made,
and possibly some other parts too.  That code should be 64bit clean
now (due to x86-64 sharing it), but there may still be some gotchas,
especially on weird-ass systems like what you've been playing with 8)

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

      reply	other threads:[~2003-01-29 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 15:23 no more MTRRs available ? Stephan von Krawczynski
     [not found] ` <Pine.LNX.4.44.0301291025240.18828-100000@coffee.psychology.mcmaster.ca>
2003-01-29 15:45   ` Stephan von Krawczynski
     [not found]     ` <Pine.LNX.4.44.0301291046490.18828-100000@coffee.psychology.mcmaster.ca>
2003-01-29 16:05       ` Stephan von Krawczynski
2003-01-29 16:20         ` Dave Jones
2003-01-29 17:15           ` Stephan von Krawczynski
2003-01-29 16:14     ` Dave Jones
2003-01-29 16:52       ` Dave Jones
2003-01-29 17:20     ` William Lee Irwin III
2003-01-29 17:48       ` Dave Jones
2003-01-29 18:00         ` William Lee Irwin III
2003-01-29 18:12           ` Dave Jones [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=20030129181215.GF1856@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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