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 14:42:59 +0100 [thread overview]
Message-ID: <4D626BE3.8030800@amd.com> (raw)
In-Reply-To: <20110221132002.GA13858@panix.com>
Brian Marcotte wrote:
>> 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.
>
> I suppose that Xen could arrange the cpu to node mapping such that
> the memoryless CPUs were assigned to the "nearest" node making it so
> you could benefit from the shared L3 cache.
>
> I don't know that it's worth anyone's time though. Perhaps a warning
> would suffice?
I also considered more possible action back then, but found that it is
probably not worth the effort, as this kind of configuration was
considered kind of bogus. But a warning message sounds like a good idea.
>
>> Do you have only 4 DIMMs?
>
> Yes, but I don't expect that to last too long. We find that over the
> lifetime of a machine, we max out the RAM slots long before we run out
> of CPU. The second CPU is mostly just so we can (eventually) fill all
> the RAM slots. It's not a problem to run with one CPU for while. I may
> also just pin the domains to particular CPU cores rather than pull the
> CPU.
Yes, just put all the DIMMs in the blue slots of the first CPU and boot
Xen with maxcpus=8. This should give you the best results without much
fiddling with the hardware.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
prev parent reply other threads:[~2011-02-21 13:42 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
2011-02-21 13:20 ` Brian Marcotte
2011-02-21 13:42 ` Andre Przywara [this message]
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=4D626BE3.8030800@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.