public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lawrence E. Freil" <lef@freil.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Serious Kernel slowdown with HIMEM (4Gig) in 2.6.7
Date: Mon, 16 Aug 2004 09:23:40 -0400	[thread overview]
Message-ID: <200408161323.i7GDNeod020199@dogwood.freil.com> (raw)

Iteresting idea, here is the /proc/mtrr output:

reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg01: base=0x20000000 ( 512MB), size= 256MB: write-back, count=1
reg02: base=0x30000000 ( 768MB), size= 128MB: write-back, count=1
reg03: base=0x38000000 ( 896MB), size=  64MB: write-back, count=1
reg04: base=0x3c000000 ( 960MB), size=  32MB: write-back, count=1
reg05: base=0x3e000000 ( 992MB), size=  16MB: write-back, count=1
reg06: base=0xf0000000 (3840MB), size=   2MB: write-combining, count=1

The memory in question is the block from 896 to 1Gig.  Looks pretty
normal.

At this point I need to recompile "ls" with full profiling and time it
with and without extended memory.  I have a suspicion that it is related
to "mmap" on data in a high memory buffer.  It does not effect actual
file read/write.  Performance on that is pretty much the same.

>On Sat, Aug 14, 2004 at 12:43:11PM -0400, Lawrence E. Freil wrote:
>> Though there is a consistant sys component that is slightly higher.  I ran
>> profiles three times for "fast" and three times for "slow".  Here they are
>
>Try cat /proc/mtrr.  I bet your system isn't marking some of its RAM 
>cachable in the MTRRs.
>
>		-ben

-- 
        Lawrence Freil                      Email:lef@freil.com
        1768 Old Country Place              Phone:(770) 667-9274
        Woodstock, GA 30188



             reply	other threads:[~2004-08-16 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 13:23 Lawrence E. Freil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-16 18:43 Serious Kernel slowdown with HIMEM (4Gig) in 2.6.7 Mikael Pettersson
2004-08-16 17:40 Lawrence E. Freil
2004-08-14 16:43 Lawrence E. Freil
2004-08-15 15:04 ` Benjamin LaHaise
2004-08-14 15:43 Lawrence E. Freil
2004-08-14  2:11 Lawrence E. Freil
2004-08-14  4:18 ` Darren Williams
2004-08-14 11:42   ` Lawrence E. Freil
2004-08-14 15:09   ` Lawrence E. Freil
2004-08-14  8:51 ` William Lee Irwin III
2004-08-14 15:09 ` Martin J. Bligh

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=200408161323.i7GDNeod020199@dogwood.freil.com \
    --to=lef@freil.com \
    --cc=linux-kernel@vger.kernel.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