From: Brian Marcotte <marcotte@panix.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Brian Marcotte <marcotte@panix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: NUMA problem with AMD G34 system
Date: Mon, 21 Feb 2011 06:29:58 -0500 [thread overview]
Message-ID: <20110221112958.GA25000@panix.com> (raw)
In-Reply-To: <4D6226F0.1080007@amd.com>
> 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.
In this case, I suppose I'll remove a CPU and rearrange the memory
until it's time to add more memory.
Thanks.
--
- Brian
next prev parent reply other threads:[~2011-02-21 11:29 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 [this message]
2011-02-21 11:51 ` Andre Przywara
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=20110221112958.GA25000@panix.com \
--to=marcotte@panix.com \
--cc=andre.przywara@amd.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.