[XEND] Be more generous with the default shadow allocation.

Allow enough shadow memory to avoid thrashing the shadow pages,
rather than just enough for safety.
Signed-off-by: Tim Deegan <Tim.Deegan@xensource.com>
This commit is contained in:
Tim Deegan committed 2006-10-25 11:44:58 +01:00
1 parent e481cc001d
commit 3df1dee7fb
1 file changed
+6 -3
+6 -3
View File
@@ -500,9 +500,12 @@ class X86_HVM_ImageHandler(HVMImageHandler):
# overhead due to getRequiredInitialReservation.
maxmem_kb = self.getRequiredInitialReservation(maxmem_kb)
# 1MB per vcpu plus 4Kib/Mib of RAM. This is higher than
# the minimum that Xen would allocate if no value were given.
return max(1024 * self.vm.getVCpuCount() + maxmem_kb / 256,
# 256 pages (1MB) per vcpu,
# plus 1 page per MiB of RAM for the P2M map,
# plus 1 page per MiB of RAM to shadow the resident processes.
# This is higher than the minimum that Xen would allocate if no value
# were given (but the Xen minimum is for safety, not performance).
return max(4 * (256 * self.vm.getVCpuCount() + 2 * (maxmem_kb / 1024)),
shadow_mem_kb)
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.