From: Dan Williams <dan.j.williams@intel.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Pankaj Gupta <pagupta@redhat.com>, KVM list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Rik van Riel <riel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kwolf@redhat.com, Haozhong Zhang <haozhong.zhang@intel.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>
Subject: Re: [Qemu-devel] KVM "fake DAX" device flushing
Date: Thu, 11 May 2017 12:15:43 -0700 [thread overview]
Message-ID: <CAPcyv4irL+imcaWBtHox9oUatndpRw-3xfxtTcn1NV58iph+og@mail.gmail.com> (raw)
In-Reply-To: <20170511181703.GC8701@stefanha-x1.localdomain>
On Thu, May 11, 2017 at 11:17 AM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Wed, May 10, 2017 at 09:26:00PM +0530, Pankaj Gupta wrote:
>> We are sharing initial project proposal for
>> 'KVM "fake DAX" device flushing' project for feedback.
>> Got the idea during discussion with 'Rik van Riel'.
>
> CCing NVDIMM folks.
>
>>
>> Also, request answers to 'Questions' section.
>>
>> Abstract :
>> ----------
>> Project idea is to use fake persistent memory with direct
>> access(DAX) in virtual machines. Overall goal of project
>> is to increase the number of virtual machines that can be
>> run on a physical machine, in order to increase the density
>> of customer virtual machines.
>>
>> The idea is to avoid the guest page cache, and minimize the
>> memory footprint of virtual machines. By presenting a disk
>> image as a nvdimm direct access (DAX) memory region in a
>> virtual machine, the guest OS can avoid using page cache
>> memory for most file accesses.
How is this different than the solution that Clear Containers came up with?
https://lwn.net/Articles/644675/
next prev parent reply other threads:[~2017-05-11 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 15:56 [Qemu-devel] KVM "fake DAX" device flushing Pankaj Gupta
2017-05-11 18:17 ` Stefan Hajnoczi
2017-05-11 19:15 ` Dan Williams [this message]
2017-05-11 21:35 ` Rik van Riel
2017-05-11 21:38 ` Rik van Riel
2017-05-12 13:42 ` Stefan Hajnoczi
2017-05-12 16:53 ` Kevin Wolf
2017-05-15 9:12 ` Stefan Hajnoczi
2017-05-12 6:56 ` Pankaj Gupta
2017-05-11 22:06 ` Dan Williams
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=CAPcyv4irL+imcaWBtHox9oUatndpRw-3xfxtTcn1NV58iph+og@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=haozhong.zhang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@redhat.com \
--cc=stefanha@redhat.com \
--cc=xiaoguangrong.eric@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;
as well as URLs for NNTP newsgroup(s).