Hi Jingke.
Although I haven't digged into it and I'm not sure, I suppose
that Linux/ia64 may round up/down usable memory when parsing efi
memory map.
Presumably looking into /proc/iomem may help to track down
the issue.
thanks,
On Wed, Jul 09, 2008 at 01:36:19PM +0800, Zhang, Jingke wrote:
> Hi all,
> When we check the "/proc/meminfo" in the VTI, we found the total
> memory is about 100MB less than what we config. For x86_64 and KVM side,
> they are different. So, I want to ask a question: Is there any feature
> reserving much memory of VTI? Thank you very much!
>
> BTW, by command "dmesg | grep reserve":
> For RHEL4u4 VTI ------ Memory: 942976k/1018784k available (5714k
> code, 87712k reserved, 2279k data, 384k init)
> For RHEL4u4 x86_64 VMX ------ Memory: 1024844k/1048544k available
> (2105k kernel code, 0k reserved, 1297k data, 196k init)
> For RHEL4u4 x86_64 KVM ------ Memory: 1024772k/1048512k available
> (2105k kernel code, 0k reserved, 1297k data, 196k init)
>
>
> Thanks,
> Zhang Jingke
>
>
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
>
--
yamahata
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|