All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	Dan Magenheimer <dan.magenheimer@oracle.com>,
	mtosatti@redhat.com, gregkh@linuxfoundation.org,
	sjenning@linux.vnet.ibm.com, Konrad Wilk <konrad.wilk@oracle.com>,
	kvm@vger.kernel.org
Subject: Re: [RFC 00/10] KVM: Add TMEM host/guest support
Date: Tue, 12 Jun 2012 15:01:36 +0300	[thread overview]
Message-ID: <4FD72FA0.1060104@redhat.com> (raw)
In-Reply-To: <20120612115857.GT580@redhat.com>

On 06/12/2012 02:58 PM, Gleb Natapov wrote:
> On Tue, Jun 12, 2012 at 02:46:38PM +0300, Avi Kivity wrote:
>> On 06/11/2012 10:56 PM, Sasha Levin wrote:
>> > 
>> > btw, so far we've been poking on half of the code here.
>> > 
>> > What about frontswap over kvm-tmem? are there any specific tests you'd
>> > like to see there?
>> 
>> hmm.  On one hand, no one swaps these days so there aren't any good
>> benchmarks for it.  On the other hand, with swapping, at least we're
>> guaranteed the page will be read in the future (unlike cache, where it's
>> quite possible it won't be).  I don't know.
>> 
>> 
> Swapped page can be discarded without reading too.

Right.

The effects of frontswap can be achieved by swapping to a block device
that sets cache=writeback, more or less (esp. with trim support, you can
discard pages that you won't be needing again before they hit disk).


-- 
error compiling committee.c: too many arguments to function



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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06 13:07 [RFC 00/10] KVM: Add TMEM host/guest support Sasha Levin
2012-06-06 13:24 ` Avi Kivity
2012-06-08 13:20   ` Sasha Levin
2012-06-08 16:06     ` Dan Magenheimer
2012-06-11 11:17       ` Avi Kivity
2012-06-11  8:09     ` Avi Kivity
2012-06-11 10:26       ` Sasha Levin
2012-06-11 11:45         ` Avi Kivity
2012-06-11 15:44           ` Dan Magenheimer
2012-06-11 17:06             ` Avi Kivity
2012-06-11 19:25               ` Sasha Levin
2012-06-11 19:56                 ` Sasha Levin
2012-06-12 11:46                   ` Avi Kivity
2012-06-12 11:58                     ` Gleb Natapov
2012-06-12 12:01                       ` Avi Kivity [this message]
2012-06-12 10:12                 ` Avi Kivity
2012-06-12  1:18               ` Dan Magenheimer
2012-06-12 10:09                 ` Avi Kivity
2012-06-12 16:40                   ` Dan Magenheimer
2012-06-12 17:54                     ` 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=4FD72FA0.1060104@redhat.com \
    --to=avi@redhat.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=gleb@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --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 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.