mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: x86/NUMA: Reason for ignoring too small NUMA nodes?
Date: Mon, 9 Nov 2009 13:27:15 +0100	[thread overview]
Message-ID: <4AF80AA3.9020400@amd.com> (raw)

Hi Andi,

while experimenting with a system with a memory-less NUMA node I 
stumbled upon code in the Linux kernel which ignores nodes containing 
less than a certain amount of RAM, obviously to fix systems with a buggy 
BIOS.
Can you elaborate on this? What kind of incorrect entry have you seen?
To correctly map the memory less node I did a patch to accept at least 
nodes with exactly zero bytes of memory (read: no SRAT memory entry), 
was this special condition also present in the buggy machines?
Another comments reads:
      /*
      * Don't confuse VM with a node that doesn't have the
      * minimum amount of memory:
      */
Is that still a valid statement? How can the VM get confused by a node 
with already exhausted memory resources?
(found in arch/x86/mm/{srat,numa}_64.c)

I'd be grateful for some hints!

Thanks,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


             reply	other threads:[~2009-11-09 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 12:27 Andre Przywara [this message]
2009-11-09 12:38 ` Andi Kleen

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=4AF80AA3.9020400@amd.com \
    --to=andre.przywara@amd.com \
    --cc=andi@firstfloor.org \
    --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

all inboxes | Powered by JetHome®