public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Akshay Karle <akshay.a.karle@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Dan Magenheimer <dan.magenheimer@oracle.com>,
	konrad.wilk@oracle.com, kvm@vger.kernel.org,
	ashu tripathi <er.ashutripathi@gmail.com>,
	nishant gulhane <nishant.s.gulhane@gmail.com>,
	amarmore2006 <amarmore2006@gmail.com>,
	Shreyas Mahure <shreyas.mahure@gmail.com>,
	mahesh mohan <mahesh6490@gmail.com>
Subject: Re: [RFC 0/2] kvm: Transcendent Memory (tmem) on KVM
Date: Thu, 15 Mar 2012 18:58:40 +0200	[thread overview]
Message-ID: <4F621FC0.7050800@redhat.com> (raw)
In-Reply-To: <1331224181.2585.16.camel@aks>

On 03/08/2012 06:29 PM, Akshay Karle wrote:
> Hi,
>
> We are undergraduate engineering students of Maharashtra Academy of
> Engineering, Pune, India and we are working on a project entitled
> 'Transcendent Memory on KVM' as a part of our academics.
> The project members are:
> 1. Ashutosh Tripathi
> 2. Shreyas Mahure
> 3. Nishant Gulhane
> 4. Akshay Karle
>
> ---
> Project Description:
> What is Transcendent Memory(tmem in short)?
> Transcendent Memory is a memory optimization technique for the
> virtualized environment. It collects the underutilized memory of the
> guests and the unassigned(fallow) memory of the host and places it into
> a central tmem pool. Indirect access to this pool is then provided to the guests.
> For further information on tmem, please refer the article on lwn by Dr.
> Dan Magenheimer:
> http://lwn.net/Articles/454795/
>
> Since kvm is one of the most popular hypervisors available,
> we decided to implement this technique for kvm.
>
> Any comments/feedback would be appreciated and will help us a lot with our work.
>

One of the potential problems with tmem is reduction in performance when
the cache hit rate is low, for example when streaming.

Can you test this by creating a large file, for example with

  dd < /dev/urandom > file bs=1M count=100000

and then measuring the time to stream it, using

  time dd < file > /dev/null

with and without the patch?

Should be done on a cleancache enabled guest filesystem backed by a
virtio disk with cache=none.

It would be interesting to compare kvm_stat during the streaming, with
and without the patch.

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


  parent reply	other threads:[~2012-03-15 16:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 16:29 [RFC 0/2] kvm: Transcendent Memory (tmem) on KVM Akshay Karle
2012-03-15 16:42 ` Konrad Rzeszutek Wilk
2012-03-15 16:48 ` Konrad Rzeszutek Wilk
2012-03-15 16:58 ` Avi Kivity [this message]
2012-03-15 17:49   ` Dan Magenheimer
2012-03-15 18:01     ` Avi Kivity
2012-03-15 18:02       ` Konrad Rzeszutek Wilk
2012-03-15 18:10         ` Avi Kivity
2012-03-15 19:36           ` Dan Magenheimer
2012-03-15 19:46             ` Konrad Rzeszutek Wilk
2012-03-15 19:16         ` Dan Magenheimer

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=4F621FC0.7050800@redhat.com \
    --to=avi@redhat.com \
    --cc=akshay.a.karle@gmail.com \
    --cc=amarmore2006@gmail.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=er.ashutripathi@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh6490@gmail.com \
    --cc=nishant.s.gulhane@gmail.com \
    --cc=shreyas.mahure@gmail.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