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

Re: [Xen-users] Serious performance problems - is Xen not ready for prod

To: Xuehai Zhang <hai@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Serious performance problems - is Xen not ready for production use?
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Fri, 15 Jul 2005 01:37:52 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Patrick Hess <posi@xxxxxxx>
Delivery-date: Fri, 15 Jul 2005 00:31:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0507141616250.16341@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <42D4D8F4.4040106@xxxxxxx> <200507141541.47091.mark.williamson@xxxxxxxxxxxx> <Pine.LNX.4.58.0507141616250.16341@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.1
> My experiment shows changing "mem=268435456" to "mem=256m" doesn't
> help with the ballooning above initial allocation problem.
> (Linux BootPrompt-Howto
> (http://en.tldp.org/HOWTO/BootPrompt-HOWTO-3.html#ss3.3)
> suggests both "k" and "m" suffixes can be used for "mem=" argument).

Yep, that's the syntax I would expect for a kernel arg: I don't think this is 
responsible for the ballooning problem though - that error must be somewhere 
else in the code.

> BTW, i still think "mem=268435456" is a valid configuration to give memory
> in bytes. Both "dmesg" and "free" outputs form the domain booted with this
> configuration show the domain is booted with 256MB memory.

I meant the issue Patrick saw: he had the right amount of memory but none of 
it was free.  I was suspicious that it might all be taken up by kernel data 
structures.

Did you see lots of memory allocated out of that 256M?

Cheers,
Mark

> > I can't guess any better without going through the code - it should
> > hopefully become apparent when someone fixes the ballooning problem (does
> > anyone want to volunteer for that, btw?  It'd be useful if someone could
> > post a patch.).
> >
> > Cheers,
> > Mark
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users

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