All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Brian Marcotte <marcotte@panix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: NUMA problem with AMD G34 system
Date: Mon, 21 Feb 2011 12:51:36 +0100	[thread overview]
Message-ID: <4D6251C8.1020809@amd.com> (raw)
In-Reply-To: <20110221112958.GA25000@panix.com>

Brian Marcotte wrote:
>> The SRAT CPU table seems sane, but the memory table seems to say
>> that there is no memory on node 1 and 3, thus Xen will simply put
>> those CPUs to node 0 as it cannot cope with memory-less nodes.
> 
> Ah. I think that's what was causing my confusion. Since the cpu-to-node
> mapping was unbalanced and Xen wasn't complaining, I thought for sure
> this was a problem with Xen and newer CPUs and I'd need to help with
> debugging the problem.
I prepared Xen to handle this situation (nodes without memory) before 
the M-C launch, before that it simply crashed. I agree that it is not 
obvious that you need to populate at least 4 DIMMs per CPU.

> In this case, I suppose I'll remove a CPU and rearrange the memory
> until it's time to add more memory.
Do you have only 4 DIMMs? If yes, you could do so if you can cope with 
half of the CPU power.
If you don't want to sacrifice the second CPU, you could go ahead and 
use the system with this kind of strange NUMA setup. Depending on your 
workload you will benefit more from this setup, as the impact of remote 
memory on most application is not that huge (compared to less cores, at 
least).
But if you have 8 DIMMs, you should keep the second CPU and put all 
DIMMs in the blue slots.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany

  reply	other threads:[~2011-02-21 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  8:59 NUMA problem with AMD G34 system Brian Marcotte
2011-02-21  8:48 ` Andre Przywara
2011-02-21 11:29   ` Brian Marcotte
2011-02-21 11:51     ` Andre Przywara [this message]
2011-02-21 13:20       ` Brian Marcotte
2011-02-21 13:42         ` Andre Przywara

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=4D6251C8.1020809@amd.com \
    --to=andre.przywara@amd.com \
    --cc=marcotte@panix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.