kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: mtosatti@redhat.com, gregkh@linuxfoundation.org,
	sjenning@linux.vnet.ibm.com, dan.magenheimer@oracle.com,
	konrad.wilk@oracle.com, kvm@vger.kernel.org
Subject: Re: [RFC 01/10] KVM: reintroduce hc_gpa
Date: Wed, 06 Jun 2012 14:32:04 +0200	[thread overview]
Message-ID: <1338985924.3292.68.camel@lappy> (raw)
In-Reply-To: <4FCF49DF.5060004@redhat.com>

On Wed, 2012-06-06 at 15:15 +0300, Avi Kivity wrote:
> On 06/06/2012 02:45 PM, Sasha Levin wrote:
> > On Wed, 2012-06-06 at 14:38 +0300, Avi Kivity wrote:
> >> On 06/06/2012 02:32 PM, Sasha Levin wrote:
> >> > 
> >> >> and benchmark results.
> >> > 
> >> > Is there a specific test you'd like to see? My tests were based around
> >> > the "streaming test" you proposed last time this discussion came up, and
> >> > runs of 'fio' in guests.
> >> 
> >> Those are fine, thanks.
> >> 
> >> btw, IIUC, a guest can have two tmem providers: the hypervisor and
> >> zcache.  How does it choose?
> > 
> > The guest will try to use the hypervisor, unless:
> > 
> >  - 'nokvmcleancache' is passed as param - in that case cleancache will
> > use the local zcache provider.
> > 
> >  - 'nokvmfrontswap' is passed as param - in that case frontswap will use
> > the local zcache provider.
> 
> The guest may have more memory than free host memory, and its memory is
> certainly faster; but I'm not sure how to integrate this better.

Won't the free guest memory be exhausted first by regular local caching
before cleancache springs into action?


  reply	other threads:[~2012-06-06 12:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06 11:00 [RFC 01/10] KVM: reintroduce hc_gpa Sasha Levin
2012-06-06 11:00 ` [RFC 02/10] KVM: wire up the TMEM HC Sasha Levin
2012-06-06 11:00 ` [RFC 03/10] zcache: export zcache interface Sasha Levin
2012-06-06 11:00 ` [RFC 04/10] KVM: add KVM TMEM entries in the appropriate config menu entry Sasha Levin
2012-06-06 11:00 ` [RFC 05/10] KVM: bring in general tmem definitions Sasha Levin
2012-06-06 11:00 ` [RFC 06/10] zcache: move out client declaration and add a KVM client Sasha Levin
2012-06-06 11:00 ` [RFC 07/10] KVM: add KVM TMEM host side interface Sasha Levin
2012-06-29  1:59   ` Konrad Rzeszutek Wilk
2012-06-06 11:00 ` [RFC 08/10] KVM: add KVM TMEM guest support Sasha Levin
2012-06-06 11:00 ` [RFC 09/10] KVM: support guest side cleancache Sasha Levin
2012-06-06 11:00 ` [RFC 10/10] KVM: support guest side frontswap Sasha Levin
2012-06-06 11:06 ` [RFC 01/10] KVM: reintroduce hc_gpa Avi Kivity
2012-06-06 11:32   ` Sasha Levin
2012-06-06 11:38     ` Avi Kivity
2012-06-06 11:45       ` Sasha Levin
2012-06-06 12:15         ` Avi Kivity
2012-06-06 12:32           ` Sasha Levin [this message]
2012-06-06 12:37             ` Avi Kivity

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=1338985924.3292.68.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=avi@redhat.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sjenning@linux.vnet.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).