Re: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu

[Stefan de Konink <skinkie@xxxxxxxxx>]

On Tue, 29 Jul 2008, Gerd Hoffmann wrote:

> Stefan de Konink wrote:
>
> > And you don't count the 331MB virtual memory the process takes, and every
> > tapdisk that is created?
>
> Tapdisk doesn't need physical memory.  It is address space used to map
> in guest pages.

Maybe you use a different version of Xen... I'm using 3.2.1 until the Dell
patches of the 2.6.19 kernel are backported, or I get the Vanilla kernel
running on 64bits.


root      3005  0.0  0.1   8404  1012 ?        S    Jul26   0:00 xenstored
--pid-file /var/run/xenstore.pid
root      3009  0.0  1.8  99416  9936 ?        S    Jul26   0:00 python
/usr/sbin/xend start
root      3011  0.0  0.1  20540   680 ?        Sl   Jul26   0:00
xenconsoled
root      3013  0.0 10.7 242876 56492 ?        Sl   Jul26   0:01 python
/usr/sbin/xend start
root      3014  0.0  0.1  27252   904 ?        Ssl  Jul26   0:00
blktapctrl
root     13985  0.0  0.1  27332   832 ?        Sl   11:17   0:00 tapdisk
/var/run/tap/tapctrlwrite1 /var/run/tap/tap

So this looks like each disk added counts for a small megabyte of memory.
I wonder if it wouldn't be possible to run some sort of tapdisk service
that adds a mapping, instead of a lot of different processes.

The amount of memory for xend seem to increased with 7MB (from 49MB) now
this is not even close to the 32MB or 16MB value that was mentioned
before.


Stefan


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