Re: [Xen-users] Serious performance problems - is Xen not ready for production use?

[Xuehai Zhang <hai@xxxxxxxxxxxxxxx>]

On Fri, 15 Jul 2005, Mark Williamson wrote:

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

The following is the memory allocation result (commands run from inside of
the domain).

$ dmesg | grep mem
Kernel command line:
ip=128.135.164.83:1.2.3.4:128.135.164.65:255.255.255.192::eth0:off
root=/dev/sda1 ro mem=256m maxmem=256m
vmalloc area: d0800000-fbff9000, maxmem 34000000
Memory: 125376k/262144k available (1630k kernel code, 5324k reserved, 440k
data, 112k init, 0k highmem)
xen_mem: Initialising balloon driver.
Freeing unused kernel memory: 112k freed

$ free
             total       used       free     shared    buffers     cached
Mem:        256932     147452     109480          0       3072       7920
-/+ buffers/cache:     136460     120472
Swap:       204792          0     204792



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