Re: eliminating 166G limit (was Re: [Xen-devel] Problem withnr_nodes on large memory NUMA machine)

["Yinghai Lu" <yhlu.kernel@xxxxxxxxx>]

On Fri, Dec 7, 2007 at 6:20 AM, Krysan, Susan <KRYSANS@xxxxxxxxxx> wrote:
> I tested this changeset on Unisys ES7000 with 256G ram and 64 processors
> and it works:
>
> xentop - 06:30:59   Xen 3.2-unstable
> 1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0
> shutdown
> Mem: 268172340k total, 7669456k used, 260502884k free    CPUs: 64 @
> 3400MHz
>
> I will be running our full test suite on this configuration today.
>
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
> Sent: Thursday, December 06, 2007 8:40 AM
> To: eak@xxxxxxxxxx
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: eliminating 166G limit (was Re: [Xen-devel] Problem
> withnr_nodes on large memory NUMA machine)
>
> Try xen-unstable changeset 16548.

Susan,

how about TOM? i mean MMIO size...

my system with 256g/32cores, and 0xe0000000 - 0x100000000 is mmio
mtrr
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 512MB: write-back, count=1
TOM: 00000000e0000000 aka 3584M
TOM2: 0000004020000000 aka 262656M

only can work with mem=200g

mem=224g, xen kernel will say alloc_bootmem_low can not get range..

xen kernel is from

http://people.redhat.com/dzickus/el5/92.el5/x86_64/

YH

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