|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [patch 0/6] Guest page hinting version 7.
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
Subject: |
[Xen-devel] Re: [patch 0/6] Guest page hinting version 7. |
From: |
Rik van Riel <riel@xxxxxxxxxx> |
Date: |
Thu, 02 Apr 2009 16:14:33 -0400 |
Cc: |
akpm@xxxxxxxx, Nick Piggin <nickpiggin@xxxxxxxxxxxx>, frankeh@xxxxxxxxxxxxxx, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, Martin Schwidefsky <schwidefsky@xxxxxxxxxx>, hugh@xxxxxxxxxxx |
Delivery-date: |
Thu, 02 Apr 2009 13:16:14 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<49D518E9.1090001@xxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<20090327150905.819861420@xxxxxxxxxx> <200903281705.29798.rusty@xxxxxxxxxxxxxxx> <20090329162336.7c0700e9@skybase> <200904022232.02185.nickpiggin@xxxxxxxxxxxx> <20090402175249.3c4a6d59@skybase> <49D50CB7.2050705@xxxxxxxxxx> <49D518E9.1090001@xxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Thunderbird 2.0.0.21 (X11/20090320) |
Jeremy Fitzhardinge wrote:
The more complex host policy decisions of how to balance overall
memory use system-wide are much in the same for both mechanisms.
Not at all. Page hinting is just an optimization to host swapping, where
IO can be avoided on many of the pages that hit the end of the LRU.
No decisions have to be made at all about balancing memory use
between guests, it just happens through regular host LRU aging.
Automatic ballooning requires that something on the host figures
out how much memory each guest needs and sizes the guests
appropriately. All the proposed policies for that which I have
seen have some nasty corner cases or are simply very limited
in scope.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|