All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Sergey Popov <faijeya@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel
Date: Fri, 28 Sep 2007 17:40:23 -0600	[thread overview]
Message-ID: <46FD90E7.6090009@shaw.ca> (raw)
In-Reply-To: <fa.mssrRT/qBOVwvrr2k/d2or6ggOo@ifi.uio.no>

Sergey Popov wrote:
> Short description: after recompiling 32-bit kernel with 64Gb highmem
> support and rebooting into it, OS started working very much slower
> then before.
> 
> Specifications: Intel Core 2 Duo E6600@2,4Ghz on Intel i965Q-based
> motherboard. 6Gb of DDR2 RAM, 2x1Gb+2x2Gb, dual-channel.
> Vector Linux 5.8 (Slackware Linux 11-based), 2.6.20.3 kernel.
> 
> Long description: after recompiling 32-bit 2.6.20.3 kernel with 64Gb
> highmem option and rebooting into it, booting process froze on udevd.
> After booting up from CD and disabling rc.udev, system started, but
> it's work after rc.M script sarted was 5-10 times slower then usual.
> top showed, that processes are taking much more CPU% time then usual.
> I tried downloading the newest stable kernel - 2.6.22.9 - hoping, that
> it would solve the problem. I downloaded it, booted from CD, and
> compiled it with 64Gb highmem support. I felt some speed improvement,
> but if on 2.6.20.3 machine performed like P166, now it is working like
> P2-350.
> I've found a similar problem, described on lkml -
> http://lkml.org/lkml/2007/5/30/5 . But, unfortunately, it is x86_64
> related and contains no clues for me.
> 
> Moving to 64-bit distro is rather unpleasant - as there is an option
> in 32-bit kernel, it should work ;) .
> 
> What tests should I run to help investigate this problem?

Make sure your BIOS is up to date. If so, post your dmesg output and the 
contents of /proc/mtrr. There are a number of Intel boards which 
have/had BIOS bugs where the BIOS didn't set up the MTRRs to mark all 
RAM as write-back. This results in the last bit of memory being 
uncacheable and causes a major performance drop.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-09-28 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.mssrRT/qBOVwvrr2k/d2or6ggOo@ifi.uio.no>
2007-09-28 23:40 ` Robert Hancock [this message]
2007-09-28 17:15 General slowness with using 64Gb HIGHMEM option on 32-bit kernel Sergey Popov
2007-09-28  3:22 ` Nick Piggin
2007-09-28 17:46 ` Chuck Ebbert
2007-09-28 17:57   ` Sergey Popov
2007-09-28 18:03     ` Rik van Riel

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=46FD90E7.6090009@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=faijeya@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.