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-ia64-devel

Re: [Xen-ia64-devel] [PATCH] Use saner dom0 memory and vcpu defaults, d

To: Jarod Wilson <jwilson@xxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH] Use saner dom0 memory and vcpu defaults, don't panic on over-allocation
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Mon, 06 Aug 2007 07:33:17 -0600
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 06 Aug 2007 06:31:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46B5306F.8070504@xxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: HP OSLO R&D
References: <46AFF7F6.5090105@xxxxxxxxxx> <1185943424.6802.98.camel@bling> <20070801052434.GC14448%yamahata@xxxxxxxxxxxxx> <46B08EE2.5020106@xxxxxxxxxx> <46B0ACEB.3080200@xxxxxxxxxx> <46B0C21C.9010605@xxxxxxxxxx> <46B0D5AF.1050309@xxxxxxxxxx> <20070802021200.GA6395%yamahata@xxxxxxxxxxxxx> <46B1E766.7000003@xxxxxxxxxx> <46B1F9E6.9010404@xxxxxxxxxx> <46B2AFE1.6070803@xxxxxxxxxx> <46B3343A.9040106@xxxxxxxxxx> <46B34516.6030603@xxxxxxxxxx> <1186162709.6802.179.camel@bling> <46B5306F.8070504@xxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Jarod,

On Sat, 2007-08-04 at 22:05 -0400, Jarod Wilson wrote:
> After poking at the x86 code again, it looks like there's simply a guess 
> there too for extra memory to reserve. From xen/arch/x86/domain_build.c:
> 
>      /*
>       * If domain 0 allocation isn't specified, reserve 1/16th of available
>       * memory for things like DMA buffers. This reservation is clamped to
>       * a maximum of 128MB.
>       */
>      if ( dom0_nrpages == 0 )
>      {
>          dom0_nrpages = avail;
>          dom0_nrpages = min(dom0_nrpages / 16, 128L << (20 - PAGE_SHIFT));
>          dom0_nrpages = -dom0_nrpages;
>      }
> 
> 
> Based on empirical testing, it seems something along the lines of 1MB 
> per 4GB of RAM, capped at like 64MB (though probably not necessary), 
> might be sane. Its not exact of course, since memory amount doesn't 
> necessarily indicate how many PCI root bridges there are to allocate, 
> etc., but it seems to be a reasonable guess... The attached is a crack 
> at that, and on your 96G machine, should decrease the default "all" 
> memory allocation by about 24MB, allowing it to fully boot.

   I think we're going to have to go with something like this, but why
would we reduce the cap to 64MB?  I usually think of ia64 systems as
having "bigger" I/O than x86, so it seems like maybe we want to stick
with at least 128MB(?)

> Here's another thought: we could play it extra-safe, and slide that 
> allocation down another 12-24MB, and possibly even switch to allocating 
> "all" memory to dom0 by default... Then allocate all cpus too, and we'd 
> have parity with x86 here... :)

   I'm not sure I see the value in that yet.  If you have a
32/64/128/etc-way system, do you really want to have all those extra
vCPUs floating around?  Don't forget, XenSource is targeting 4-socket
systems.  In that arena, it might make sense to allocate all CPUs, but
as you scale the system up, I'm not sure it continues to make sense.
Thanks,

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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

<Prev in Thread] Current Thread [Next in Thread>