RE: 16 vcpus, 200GB of memory boots!!!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jes Sorensen wrote:
> Laurent Vivier wrote:
>> Le mercredi 15 octobre 2008 à 16:45 +0200, Jes Sorensen a écrit :
>> What is your "real" hardware (#CPU,#memory) ?
> 
> It's just a medium sized box :-) 256 cpus / 256 GB of RAM.
> 
> I have located a 512 cpu / 1 TB system in-house that I might get my
> hands on at some point to run tests on, but I need to work on the qemu
> startup times first. It took well over 20 minutes for qemu to get
> going before anything really happened.
Hi, Jes
    How long does it cost from efi shell to Linux's login interface ? Currently, we allocates so large memory for guests,  kvm has to pin the corresponding pages in p2m table other than allocate them on-demand, so it may cost long time to allocate every page from kernel, and fill them into p2m table. Once we support host-swapping later, the issue should disappear. But anyway, it can't lead into any performance issue after bootup.  To support larger memory than 384G, we may allocate contiguous huge pages, such as 16M, 256M pages for guest, if so, it may save many p2m entries because one entry can stand for 16M or 256M, so larger memory gets supported finally. 
Xiantao

> Cheers,
> Jes

--
To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux KVM Devel]     [Linux Virtualization]     [Big List of Linux Books]     [Linux SCSI]     [Yosemite Forum]

  Powered by Linux