RE: [Xen-ia64-devel] [PATCH] SMP_HOST: Alloc vhpt from domheap

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

>From: Alex Williamson 
>Sent: 2006年2月25日 5:09
>To: Xu, Anthony
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-ia64-devel] [PATCH] SMP_HOST: Alloc vhpt from domheap
>
>On Fri, 2006-02-24 at 13:58 -0700, Alex Williamson wrote:
>> On Fri, 2006-02-24 at 10:42 +0800, Xu, Anthony wrote:
>> > It's more reasonable to alloc vhpt from domheap, instead of xenheap.
>>
>> Anthony,
>>
>>    This looks to pretty significantly decrease the amount of memory
>> available to xen.  With it, I'm no longer able to boot a single 384MB
>> domU domain on a system with 1GB of memory (xminfo report 382MB
>> available).  Should the xenheap size be reduced, or are we fragmenting
>> memory somewhere with this?  Thanks,
>
>  I guess it's not as significant as I thought, w/o the patch xm info
>reports 398MB available, so I lost a granule of memory.  I still wonder
>if xenheap should be shrunk to account for this.  Thanks,
>

Total memory 1G, Dom0 uses 512M, Xenheap uses 64M, Firmware uses about 16M, the 
remainder is about 432M, It is very near with 398M, and maybe there is some 
memory lose, I'll look into it.

>I still wonder if xenheap should be shrunk to account for this.  Thanks,
Current xenheap is 64M, 16K blocks for task_struct and stack per VCPU are 
allocated from xenheap, in big machine, there are maybe 128 or 256 processors, 
in that case, 64M may be no big enough.

Since this patch has nothing to do with memory lose, Could you please check in 
this patch?  Otherwise dom0 can't boot on platform which has more than 4 
processors, when HOST-SMP is enabled.

Thanks,
Anthony

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