All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
	akpm@osdl.org, nickpiggin@yahoo.com.au, frankeh@watson.ibm.com,
	riel@redhat.com, hugh@veritas.com
Subject: Re: [patch 0/6] Guest page hinting version 7.
Date: Sun, 29 Mar 2009 16:23:36 +0200	[thread overview]
Message-ID: <20090329162336.7c0700e9@skybase> (raw)
In-Reply-To: <200903281705.29798.rusty@rustcorp.com.au>

On Sat, 28 Mar 2009 17:05:28 +1030
Rusty Russell <rusty@rustcorp.com.au> wrote:

> On Saturday 28 March 2009 01:39:05 Martin Schwidefsky wrote:
> > Greetings,
> > the circus is back in town -- another version of the guest page hinting
> > patches. The patches differ from version 6 only in the kernel version,
> > they apply against 2.6.29. My short sniff test showed that the code
> > is still working as expected.
> > 
> > To recap (you can skip this if you read the boiler plate of the last
> > version of the patches):
> > The main benefit for guest page hinting vs. the ballooner is that there
> > is no need for a monitor that keeps track of the memory usage of all the
> > guests, a complex algorithm that calculates the working set sizes and for
> > the calls into the guest kernel to control the size of the balloons.
> 
> I thought you weren't convinced of the concrete benefits over ballooning,
> or am I misremembering?

The performance test I have seen so far show that the benefits of
ballooning vs. guest page hinting are about the same. I am still
convinced that the guest page hinting is the way to go because you do
not need an external monitor. Calculating the working set size for a
guest is a challenge. With guest page hinting there is no need for a
working set size calculation.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
	akpm@osdl.org, nickpiggin@yahoo.com.au, frankeh@watson.ibm.com,
	riel@redhat.com, hugh@veritas.com
Subject: Re: [patch 0/6] Guest page hinting version 7.
Date: Sun, 29 Mar 2009 16:23:36 +0200	[thread overview]
Message-ID: <20090329162336.7c0700e9@skybase> (raw)
In-Reply-To: <200903281705.29798.rusty@rustcorp.com.au>

On Sat, 28 Mar 2009 17:05:28 +1030
Rusty Russell <rusty@rustcorp.com.au> wrote:

> On Saturday 28 March 2009 01:39:05 Martin Schwidefsky wrote:
> > Greetings,
> > the circus is back in town -- another version of the guest page hinting
> > patches. The patches differ from version 6 only in the kernel version,
> > they apply against 2.6.29. My short sniff test showed that the code
> > is still working as expected.
> > 
> > To recap (you can skip this if you read the boiler plate of the last
> > version of the patches):
> > The main benefit for guest page hinting vs. the ballooner is that there
> > is no need for a monitor that keeps track of the memory usage of all the
> > guests, a complex algorithm that calculates the working set sizes and for
> > the calls into the guest kernel to control the size of the balloons.
> 
> I thought you weren't convinced of the concrete benefits over ballooning,
> or am I misremembering?

The performance test I have seen so far show that the benefits of
ballooning vs. guest page hinting are about the same. I am still
convinced that the guest page hinting is the way to go because you do
not need an external monitor. Calculating the working set size for a
guest is a challenge. With guest page hinting there is no need for a
working set size calculation.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.


  reply	other threads:[~2009-03-29 14:23 UTC|newest]

Thread overview: 105+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 15:09 [patch 0/6] Guest page hinting version 7 Martin Schwidefsky
2009-03-27 15:09 ` Martin Schwidefsky
2009-03-27 15:09 ` [patch 1/6] Guest page hinting: core + volatile page cache Martin Schwidefsky
2009-03-27 15:09   ` Martin Schwidefsky
2009-03-27 22:57   ` Rik van Riel
2009-03-27 22:57     ` Rik van Riel
2009-03-29 13:56     ` Martin Schwidefsky
2009-03-29 13:56       ` Martin Schwidefsky
2009-03-29 14:35       ` Rik van Riel
2009-03-29 14:35         ` Rik van Riel
2009-03-27 15:09 ` [patch 2/6] Guest page hinting: volatile swap cache Martin Schwidefsky
2009-03-27 15:09   ` Martin Schwidefsky
2009-04-01  2:10   ` Rik van Riel
2009-04-01  2:10     ` Rik van Riel
2009-04-01  8:13     ` Martin Schwidefsky
2009-04-01  8:13       ` Martin Schwidefsky
2009-03-27 15:09 ` [patch 3/6] Guest page hinting: mlocked pages Martin Schwidefsky
2009-03-27 15:09   ` Martin Schwidefsky
2009-04-01  2:52   ` Rik van Riel
2009-04-01  2:52     ` Rik van Riel
2009-04-01  8:13     ` Martin Schwidefsky
2009-04-01  8:13       ` Martin Schwidefsky
2009-03-27 15:09 ` [patch 4/6] Guest page hinting: writable page table entries Martin Schwidefsky
2009-03-27 15:09   ` Martin Schwidefsky
2009-04-01 13:25   ` Rik van Riel
2009-04-01 13:25     ` Rik van Riel
2009-04-01 14:36     ` Martin Schwidefsky
2009-04-01 14:36       ` Martin Schwidefsky
2009-04-01 14:45       ` Rik van Riel
2009-04-01 14:45         ` Rik van Riel
2009-03-27 15:09 ` [patch 5/6] Guest page hinting: minor fault optimization Martin Schwidefsky
2009-03-27 15:09   ` Martin Schwidefsky
2009-04-01 15:33   ` Rik van Riel
2009-04-01 15:33     ` Rik van Riel
2009-03-27 15:09 ` [patch 6/6] Guest page hinting: s390 support Martin Schwidefsky
2009-03-27 15:09   ` Martin Schwidefsky
2009-04-01 16:18   ` Rik van Riel
2009-04-01 16:18     ` Rik van Riel
2009-03-27 23:03 ` [patch 0/6] Guest page hinting version 7 Dave Hansen
2009-03-27 23:03   ` Dave Hansen
2009-03-28  0:06   ` Rik van Riel
2009-03-28  0:06     ` Rik van Riel
2009-03-29 14:20     ` Martin Schwidefsky
2009-03-29 14:20       ` Martin Schwidefsky
2009-03-29 14:38       ` Rik van Riel
2009-03-29 14:38         ` Rik van Riel
2009-03-29 14:12   ` Martin Schwidefsky
2009-03-29 14:12     ` Martin Schwidefsky
2009-03-30 15:54     ` Dave Hansen
2009-03-30 15:54       ` Dave Hansen
2009-03-30 16:34       ` Martin Schwidefsky
2009-03-30 16:34         ` Martin Schwidefsky
2009-03-30 18:37       ` Jeremy Fitzhardinge
2009-03-30 18:37         ` Jeremy Fitzhardinge
2009-03-30 18:42         ` Rik van Riel
2009-03-30 18:42           ` Rik van Riel
2009-03-30 18:59           ` Jeremy Fitzhardinge
2009-03-30 18:59             ` Jeremy Fitzhardinge
2009-03-30 20:02             ` Rik van Riel
2009-03-30 20:02               ` Rik van Riel
2009-03-30 20:35               ` Jeremy Fitzhardinge
2009-03-30 20:35                 ` Jeremy Fitzhardinge
2009-03-30 21:38                 ` Dor Laor
2009-03-30 21:38                   ` Dor Laor
2009-03-30 22:16                   ` Izik Eidus
2009-03-30 22:16                     ` Izik Eidus
2009-03-28  6:35 ` Rusty Russell
2009-03-28  6:35   ` Rusty Russell
2009-03-29 14:23   ` Martin Schwidefsky [this message]
2009-03-29 14:23     ` Martin Schwidefsky
2009-04-02 11:32     ` Nick Piggin
2009-04-02 11:32       ` Nick Piggin
2009-04-02 15:52       ` Martin Schwidefsky
2009-04-02 15:52         ` Martin Schwidefsky
2009-04-02 16:18         ` Jeremy Fitzhardinge
2009-04-02 16:18           ` Jeremy Fitzhardinge
2009-04-02 16:23         ` Nick Piggin
2009-04-02 16:23           ` Nick Piggin
2009-04-02 19:06         ` Rik van Riel
2009-04-02 19:06           ` Rik van Riel
2009-04-02 19:22           ` Nick Piggin
2009-04-02 19:22             ` Nick Piggin
2009-04-02 20:05             ` Rik van Riel
2009-04-02 20:05               ` Rik van Riel
2009-04-03  0:50               ` Jeremy Fitzhardinge
2009-04-03  0:50                 ` Jeremy Fitzhardinge
2009-04-02 19:58           ` Jeremy Fitzhardinge
2009-04-02 19:58             ` Jeremy Fitzhardinge
2009-04-02 20:14             ` Rik van Riel
2009-04-02 20:14               ` Rik van Riel
2009-04-02 20:34               ` Jeremy Fitzhardinge
2009-04-02 20:34                 ` Jeremy Fitzhardinge
2009-04-03  8:49                 ` Martin Schwidefsky
2009-04-03  8:49                   ` Martin Schwidefsky
2009-04-03 18:19                   ` Jeremy Fitzhardinge
2009-04-03 18:19                     ` Jeremy Fitzhardinge
2009-04-06  7:21                     ` Martin Schwidefsky
2009-04-06  7:21                       ` Martin Schwidefsky
2009-04-06  7:32                       ` Nick Piggin
2009-04-06  7:32                         ` Nick Piggin
2009-04-06  7:32                         ` Nick Piggin
2009-04-06 19:23                       ` Jeremy Fitzhardinge
2009-04-06 19:23                         ` Jeremy Fitzhardinge
2009-04-02 19:27         ` Hugh Dickins
2009-04-02 19:27           ` Hugh Dickins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090329162336.7c0700e9@skybase \
    --to=schwidefsky@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=frankeh@watson.ibm.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=virtualization@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.