DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com.au;
  h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
  b=OhW4436CsZ/uqPgGbCwCgSBRMhNZ7LkQZ3QU09PBWWZy2zGnhWQqq3+7H+e/QxcNOn/UbPDD3KOVobJMJMxy/mxrl1g4LB+ULN6e3Q5MDHmQqx4sfl+RKlDXF1vSt5jD5xGwB6QZjaKYHgQmBYGmBDIC4tQEtIPSrhBdIxpIUYQ=  ;
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Sergey Popov" <faijeya@gmail.com>
Subject: Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel
Date: Fri, 28 Sep 2007 13:22:44 +1000
User-Agent: KMail/1.9.5
Cc: linux-kernel@vger.kernel.org
References: <dd4eba420709281015w50bd6b0fj21f72756a962a26b@mail.gmail.com>
In-Reply-To: <dd4eba420709281015w50bd6b0fj21f72756a962a26b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200709281322.44864.nickpiggin@yahoo.com.au>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1795
Lines: 37

On Saturday 29 September 2007 03:15, 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.

It's most likely the MTRR problem that Rik mentioned.


> Moving to 64-bit distro is rather unpleasant - as there is an option
> in 32-bit kernel, it should work ;) .

If you have a gcc that can compile 64-bit code, then I found it was as
simple as doing a 'make ARCH=x86_64' and building the kernel with 32-bit
program support.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/