public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Lawrence E. Freil" <lef@freil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serious Kernel slowdown with HIMEM (4Gig) in 2.6.7
Date: Sat, 14 Aug 2004 01:51:03 -0700	[thread overview]
Message-ID: <20040814085103.GT11200@holomorphy.com> (raw)
In-Reply-To: <200408140211.i7E2BNSg027992@dogwood.freil.com>

On Fri, Aug 13, 2004 at 10:11:23PM -0400, Lawrence E. Freil wrote:
> I'm following the kernel bug reporting format so:
> 1. Linux 2.6.7 kernel slowdown in directory access with HIMEM on
> 2. I have discovered an issue with the Linux 2.6.7 kernel when HIMEM is
>    enabled which exhibits itself as a slowdown in directory access regardless
>    of filesystem used.  When HIMEM is disabled the performance returns to
>    normal.  The test I ran was a simple "/usr/bin/time ls -l" of a directory
>    with 3000 empty files.  With HIMEM enabled in the kernel this takes
>    approximately 1.5 seconds.  Without HIMEM it takes 0.03 seconds.  The
>    time is 100% CPU and no I/O operations are done to disk.  "time" reports
>    there are 460 "minor" page faults with zero "major" page faults.
>    I believe the issue here is the mapping of pages between high-mem and
>    lowmem in the kernel paging code.  This increase in time for directory
>    accesses doubles to triples times for applications using samba.
>    I have also tested this on another system which had only 512Meg of RAM
>    but with HIMEM set in the kernel and did not experience the problem.
>    I believe it only effects the performance when the paging buffers end
>    up in highmem.

Please try to reproduce this with CONFIG_HIGHMEM=y but using mem=700M
This will tell me something useful beyond "boot with less RAM".

-- wli

  parent reply	other threads:[~2004-08-14  8:51 UTC|newest]

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

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=20040814085103.GT11200@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=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