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

[Xen-devel] Re: Overcommitting memory (was: Disable auto-balloon on ia64)

To: "Charles Coffing" <ccoffing@xxxxxxxxxx>
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 22 May 2006 16:17:05 +0100
Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 May 2006 08:17:25 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>


On 22 May 2006, at 16:12, Charles Coffing wrote:

In shadow32.c, I see a FIXME comment that refers to "shadow flush".
Even if such things are done, can you put an upper limit on the runtime
memory overhead for an HVM domain?

Yes, it ought to be a space/time tradeoff. The shadow pagetables shouldbe regarded merely as a cache. However, the current shadow mode'smemory handling sucks.


 -- Keir


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

References:
- [Xen-devel] [PATCH] Disable auto-balloon on ia64
  - From: Tian, Kevin
- [Xen-devel] Re: [PATCH] Disable auto-balloon on ia64
  - From: Keir Fraser
- [Xen-devel] Overcommitting memory (was: Disable auto-balloon on ia64)
  - From: Charles Coffing

Prev by Date: Re: [Xen-devel] [PATCH] Fix auto-ballooning of dom0 for HVM domains
Next by Date: RE: [Xen-devel] [PATCH] Make "xm mem-set" be lower boundondomX-min-mem
Previous by thread: [Xen-devel] Overcommitting memory (was: Disable auto-balloon on ia64)
Next by thread: [Xen-devel] [RESEND] Question about recursive mappings
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.