From: Pankaj Gupta <pagupta@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Jan Kara <jack@suse.cz>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
KVM list <kvm@vger.kernel.org>, Rik van Riel <riel@surriel.com>,
linux-nvdimm <linux-nvdimm@ml01.01.org>,
David Hildenbrand <david@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Christoph Hellwig <hch@infradead.org>,
Vishal L Verma <vishal.l.verma@intel.com>,
Igor Mammedov <imammedo@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
zwisler@kernel.org, lcapitulino@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>,
Nitesh Narayan Lal <nilal@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] kvm "fake DAX" device
Date: Sat, 13 Oct 2018 12:29:12 -0400 (EDT) [thread overview]
Message-ID: <2107404743.20781403.1539448152851.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAPcyv4gEVxoNFUmFctSR6nRku_Pcz2GfXB+-iHBARmc+Wa+dfQ@mail.gmail.com>
> >
> > This patch series has implementation for "fake DAX".
> > "fake DAX" is fake persistent memory(nvdimm) in guest
> > which allows to bypass the guest page cache. This also
> > implements a VIRTIO based asynchronous flush mechanism.
>
> Can we stop calling this 'fake DAX', because it isn't 'DAX' and it's
> starting to confuse people. This enabling is effectively a
> host-page-cache-passthrough mechanism not DAX. Let's call the whole
> approach virtio-pmem, and leave DAX out of the name to hopefully
> prevent people from wondering why some DAX features are disabled with
> this driver. For example MAP_SYNC is not compatible with this
> approach.
Sure. I got your point. I will use "virtio-pmem" in future.
>
> Additional enabling is need to disable MAP_SYNC in the presence of a
> virtio-pmem device. See the rough proposal here:
>
> https://lkml.org/lkml/2018/4/25/756
Yes, I will handle disabling of MAP_SYNC for this use-case.
Thanks,
Pankaj
prev parent reply other threads:[~2018-10-13 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 5:00 [PATCH v2 0/2] kvm "fake DAX" device Pankaj Gupta
2018-10-13 5:00 ` [PATCH v2 1/2] libnvdimm: nd_region flush callback support Pankaj Gupta
2018-10-13 8:31 ` kbuild test robot
2018-10-13 9:38 ` kbuild test robot
2018-10-13 5:00 ` [PATCH v2 2/2] virtio-pmem: Add virtio pmem driver Pankaj Gupta
2018-10-13 16:10 ` Dan Williams
2018-10-17 19:11 ` [Qemu-devel] " Pankaj Gupta
2018-10-17 19:36 ` Dan Williams
2018-10-18 1:44 ` Pankaj Gupta
2018-10-13 16:06 ` [PATCH v2 0/2] kvm "fake DAX" device Dan Williams
2018-10-13 16:29 ` Pankaj Gupta [this message]
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=2107404743.20781403.1539448152851.JavaMail.zimbra@redhat.com \
--to=pagupta@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=hch@infradead.org \
--cc=imammedo@redhat.com \
--cc=jack@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mst@redhat.com \
--cc=nilal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@surriel.com \
--cc=stefanha@redhat.com \
--cc=vishal.l.verma@intel.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=zwisler@kernel.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 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).