WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] NUMA problem with AMD G34 system

To: Andre Przywara <andre.przywara@xxxxxxx>
Subject: Re: [Xen-devel] NUMA problem with AMD G34 system
From: Brian Marcotte <marcotte@xxxxxxxxx>
Date: Mon, 21 Feb 2011 08:20:02 -0500
Cc: Brian Marcotte <marcotte@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 21 Feb 2011 05:22:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D6251C8.1020809@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110219085932.E08B624258@xxxxxxxxxxxxxxxx> <4D6226F0.1080007@xxxxxxx> <20110221112958.GA25000@xxxxxxxxx> <4D6251C8.1020809@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
> 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?

> 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.

Thanks for your help.

--
- Brian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel