Akio Takebe wrote: [Mon Oct 02 2006, 08:45:22AM EDT]
> The following data is /proc/budddyinfo after starting each daemons.
> 1. buddyinfo of ia64 at the boottime. (dom0_mem=512MB)
> Mon Oct 2 20:42:24 JST 2006
> ---iptables--- Node 0, zone DMA 1 2 1 1 1 1 0 0 0 1 9
> ---portmap--- Node 0, zone DMA 0 1 1 1 1 0 1 0 1 0 1
> ---ssh--- Node 0, zone DMA 1 3 9 3 1 1 1 1 0 0 0
> ---sendmail--- Node 0, zone DMA 19 7 5 1 5 1 0 1 0 0 0
> ---haldaemon--- Node 0, zone DMA 20 10 5 1 4 0 1 1 0 0 0
These numbers seem considerably smaller than x86, even from the
start!
> 2. buddyinfo of x86 at the boottime. (dom0_mem=128MB)
>
> ---iptables--- Node 0, zone DMA 47 11 4 1 0 1 8 4 1 0 11
> ---portmap--- Node 0, zone DMA 3 2 0 1 0 0 1 0 1 1 9
> ---ssh--- Node 0, zone DMA 23 3 1 1 1 1 1 3 2 0 3
> ---sendmail--- Node 0, zone DMA 26 5 4 0 0 0 4 3 3 1 1
> ---haldaemon--- Node 0, zone DMA 44 14 23 14 2 1 1 0 1 0 0
> ---before xend--- Node 0, zone DMA 22 25 24 14 2 1 1 0 1 0 0
x86 should also have a Normal zone (i.e. non-DMA) which probably has
even more available, but doesn't appear in this output. I'm guessing
that the netbk and blkbk drivers aren't limited to DMA-capable pages.
> I think fragmentations of ia64 is a little quickly.
> But allocate of oder:8 is hard on also x86 at the starting of xend.
>
> My Xen/IA64 environment have 16 cpus(4 sockets, 8cores, 16threads),
> and Xen/x86 environment have 2core cpus(1 sockets, 2cores).
> The difference of the fragmentations may be caused by the number of cpus.
> What do you think about it?
My ia64 test machine has only 2 cpus, so I don't think that's the only
factor. But your data is very interesting, thanks for collecting it!
Regards,
Aron
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home