From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Cc: Sergei Haller <Sergei.Haller@math.uni-giessen.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Andi Kleen <ak@muc.de>
Subject: Re: lost memory on a 4GB amd64
Date: Fri, 22 Oct 2004 10:26:22 +0100 [thread overview]
Message-ID: <200410221026.22531.andrew@walrond.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0410221053390.17491@fb07-2go.math.uni-giessen.de>
On Friday 22 Oct 2004 09:59, Sergei Haller wrote:
>
> If I disable NUMA in 2.6.8.1, it works stable!
>
> The same with 2.6.9, which is out for a few days: if NUMA is disabled,
> everything's find, if NUMA is enabled, the kernel crashes (as described in
> previous mails)
>
> What is this NUMA by the way? Is it OK to live without?
>
Non uniform memory architecture. Basically, some of the ram is attached to
cpu1 and some to cpu2. They can still access each others ram using
HyperTransport, but can access their own ram faster. I'm no expert, but I
guess that the NUMA code tries to achieve persistent process cpu affinity and
keep all process memory in the relevant cpu's NUMA ram bank. Or something :)
Your board isn't numa, in the sense that all the ram is attached to one cpu,
but I don't think that it should break when NUMA is enabled.
I've cc'ed Andi Kleen (x86_64 supremo) who might have some insights, but I'm
guessing he'll say "Bios problem - tough luck". I might be wrong ;)
Andrew Walrond
next prev parent reply other threads:[~2004-10-22 9:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 4:48 Sergei Haller
2004-09-16 13:30 ` Andrew Walrond
2004-09-16 13:48 ` Andrew Walrond
2004-09-16 14:09 ` Sergei Haller
2004-09-16 14:28 ` Andrew Walrond
2004-09-16 14:56 ` Sergei Haller
2004-09-16 15:19 ` Andrew Walrond
2004-09-16 15:52 ` Sergei Haller
2004-09-18 14:18 ` Sergei Haller
2004-09-19 20:01 ` Jon Masters
2004-09-19 21:47 ` Sergei Haller
2004-09-19 22:00 ` Jon Masters
2004-09-19 22:19 ` Sergei Haller
2004-09-20 10:26 ` Sergei Haller
2004-09-24 4:38 ` Sergei Haller
2004-09-24 8:15 ` Andrew Walrond
2004-09-24 8:23 ` Sergei Haller
2004-09-24 8:31 ` Andrew Walrond
2004-09-24 8:57 ` Sergei Haller
2004-09-24 9:27 ` Rafael J. Wysocki
2004-09-24 9:41 ` Andrew Walrond
2004-09-24 11:42 ` Sergei Haller
2004-09-24 12:15 ` Andrew Walrond
2004-10-22 8:59 ` Sergei Haller
2004-10-22 9:26 ` Andrew Walrond [this message]
2004-10-22 18:24 ` Andi Kleen
2004-10-23 10:02 ` Andreas Klein
2004-10-23 16:43 ` Andi Kleen
2004-10-26 11:25 ` Andreas Klein
2004-10-23 10:26 ` Sergei Haller
2004-10-23 16:49 ` Andi Kleen
2004-10-24 9:53 ` Sergei Haller
[not found] ` <Pine.LNX.4.58.0410271704050.3903@pluto.physik.uni-wuerzburg.de>
2004-10-27 15:39 ` solution " Sergei Haller
2004-10-27 16:05 ` Andreas Klein
2004-10-27 16:17 ` Sergei Haller
2004-10-28 13:32 ` Andreas Klein
2004-10-27 16:44 ` linux-os
2004-10-27 17:47 ` Andrew Walrond
2004-09-24 11:50 ` Sergei Haller
[not found] <2EWxl-7CI-13@gated-at.bofh.it>
2004-09-16 7:01 ` Andi Kleen
2004-09-16 12:15 ` Sergei Haller
2004-09-16 12:34 ` Andi Kleen
2004-09-18 14:07 ` Sergei Haller
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=200410221026.22531.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=Sergei.Haller@math.uni-giessen.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
Powered by JetHome