From: Pankaj Gupta <pagupta@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Rik van Riel <riel@redhat.com>,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
kvm-devel <kvm@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Qemu Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Nitesh Narayan Lal <nilal@redhat.com>
Subject: Re: KVM "fake DAX" flushing interface - discussion
Date: Fri, 21 Jul 2017 09:29:15 -0400 (EDT) [thread overview]
Message-ID: <46101617.33460557.1500643755247.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170721121241.GA18014@stefanha-x1.localdomain>
> > A] Problems to solve:
> > ------------------
> >
> > 1] We are considering two approaches for 'fake DAX flushing interface'.
> >
> > 1.1] fake dax with NVDIMM flush hints & KVM async page fault
> >
> > - Existing interface.
> >
> > - The approach to use flush hint address is already nacked upstream.
> >
> > - Flush hint not queued interface for flushing. Applications might
> > avoid to use it.
>
> This doesn't contradicts the last point about async operation and vcpu
> control. KVM async page faults turn the Address Flush Hints write into
> an async operation so the guest can get other work done while waiting
> for completion.
>
> >
> > - Flush hint address traps from guest to host and do an entire fsync
> > on backing file which itself is costly.
> >
> > - Can be used to flush specific pages on host backing disk. We can
> > send data(pages information) equal to cache-line size(limitation)
> > and tell host to sync corresponding pages instead of entire disk
> > sync.
>
> Are you sure? Your previous point says only the entire device can be
> synced. The NVDIMM Adress Flush Hints interface does not involve
> address range information.
Just syncing entire block device should be simple but costly. Using flush
hint address to write data which contains list/info of dirty pages to
flush requires more thought. This calls mmio write callback at Qemu side.
As per Intel (ACPI spec 6.1, Table 5-135) there is limit to max length
of data guest can write and is equal to cache line size.
>
> >
> > - This will be an asynchronous operation and vCPU control is returned
> > quickly.
> >
> >
> > 1.2] Using additional para virt device in addition to pmem device(fake dax
> > with device flush)
>
> Perhaps this can be exposed via ACPI as part of the NVDIMM standards
> instead of a separate KVM-only paravirt device.
Same reason as above. If we decide on sending list of dirty pages there is
limit to send max size of data to host using flush hint address.
>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Pankaj Gupta <pagupta@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
Qemu Developers <qemu-devel@nongnu.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Rik van Riel <riel@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
ross zwisler <ross.zwisler@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Nitesh Narayan Lal <nilal@redhat.com>,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
Haozhong Zhang <haozhong.zhang@intel.com>
Subject: Re: KVM "fake DAX" flushing interface - discussion
Date: Fri, 21 Jul 2017 09:29:15 -0400 (EDT) [thread overview]
Message-ID: <46101617.33460557.1500643755247.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170721121241.GA18014@stefanha-x1.localdomain>
> > A] Problems to solve:
> > ------------------
> >
> > 1] We are considering two approaches for 'fake DAX flushing interface'.
> >
> > 1.1] fake dax with NVDIMM flush hints & KVM async page fault
> >
> > - Existing interface.
> >
> > - The approach to use flush hint address is already nacked upstream.
> >
> > - Flush hint not queued interface for flushing. Applications might
> > avoid to use it.
>
> This doesn't contradicts the last point about async operation and vcpu
> control. KVM async page faults turn the Address Flush Hints write into
> an async operation so the guest can get other work done while waiting
> for completion.
>
> >
> > - Flush hint address traps from guest to host and do an entire fsync
> > on backing file which itself is costly.
> >
> > - Can be used to flush specific pages on host backing disk. We can
> > send data(pages information) equal to cache-line size(limitation)
> > and tell host to sync corresponding pages instead of entire disk
> > sync.
>
> Are you sure? Your previous point says only the entire device can be
> synced. The NVDIMM Adress Flush Hints interface does not involve
> address range information.
Just syncing entire block device should be simple but costly. Using flush
hint address to write data which contains list/info of dirty pages to
flush requires more thought. This calls mmio write callback at Qemu side.
As per Intel (ACPI spec 6.1, Table 5-135) there is limit to max length
of data guest can write and is equal to cache line size.
>
> >
> > - This will be an asynchronous operation and vCPU control is returned
> > quickly.
> >
> >
> > 1.2] Using additional para virt device in addition to pmem device(fake dax
> > with device flush)
>
> Perhaps this can be exposed via ACPI as part of the NVDIMM standards
> instead of a separate KVM-only paravirt device.
Same reason as above. If we decide on sending list of dirty pages there is
limit to send max size of data to host using flush hint address.
>
WARNING: multiple messages have this Message-ID (diff)
From: Pankaj Gupta <pagupta@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
Qemu Developers <qemu-devel@nongnu.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Rik van Riel <riel@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
ross zwisler <ross.zwisler@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Nitesh Narayan Lal <nilal@redhat.com>,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
Haozhong Zhang <haozhong.zhang@intel.com>
Subject: Re: [Qemu-devel] KVM "fake DAX" flushing interface - discussion
Date: Fri, 21 Jul 2017 09:29:15 -0400 (EDT) [thread overview]
Message-ID: <46101617.33460557.1500643755247.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170721121241.GA18014@stefanha-x1.localdomain>
> > A] Problems to solve:
> > ------------------
> >
> > 1] We are considering two approaches for 'fake DAX flushing interface'.
> >
> > 1.1] fake dax with NVDIMM flush hints & KVM async page fault
> >
> > - Existing interface.
> >
> > - The approach to use flush hint address is already nacked upstream.
> >
> > - Flush hint not queued interface for flushing. Applications might
> > avoid to use it.
>
> This doesn't contradicts the last point about async operation and vcpu
> control. KVM async page faults turn the Address Flush Hints write into
> an async operation so the guest can get other work done while waiting
> for completion.
>
> >
> > - Flush hint address traps from guest to host and do an entire fsync
> > on backing file which itself is costly.
> >
> > - Can be used to flush specific pages on host backing disk. We can
> > send data(pages information) equal to cache-line size(limitation)
> > and tell host to sync corresponding pages instead of entire disk
> > sync.
>
> Are you sure? Your previous point says only the entire device can be
> synced. The NVDIMM Adress Flush Hints interface does not involve
> address range information.
Just syncing entire block device should be simple but costly. Using flush
hint address to write data which contains list/info of dirty pages to
flush requires more thought. This calls mmio write callback at Qemu side.
As per Intel (ACPI spec 6.1, Table 5-135) there is limit to max length
of data guest can write and is equal to cache line size.
>
> >
> > - This will be an asynchronous operation and vCPU control is returned
> > quickly.
> >
> >
> > 1.2] Using additional para virt device in addition to pmem device(fake dax
> > with device flush)
>
> Perhaps this can be exposed via ACPI as part of the NVDIMM standards
> instead of a separate KVM-only paravirt device.
Same reason as above. If we decide on sending list of dirty pages there is
limit to send max size of data to host using flush hint address.
>
next prev parent reply other threads:[~2017-07-21 13:29 UTC|newest]
Thread overview: 176+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455443283.33337333.1500618150787.JavaMail.zimbra@redhat.com>
2017-07-21 6:56 ` KVM "fake DAX" flushing interface - discussion Pankaj Gupta
2017-07-21 6:56 ` [Qemu-devel] " Pankaj Gupta
2017-07-21 6:56 ` Pankaj Gupta
2017-07-21 9:51 ` Haozhong Zhang
2017-07-21 9:51 ` [Qemu-devel] " Haozhong Zhang
2017-07-21 9:51 ` Haozhong Zhang
2017-07-21 10:21 ` Pankaj Gupta
2017-07-21 10:21 ` [Qemu-devel] " Pankaj Gupta
2017-07-21 10:21 ` Pankaj Gupta
2017-07-21 12:12 ` Stefan Hajnoczi
2017-07-21 12:12 ` [Qemu-devel] " Stefan Hajnoczi
2017-07-21 13:29 ` Pankaj Gupta [this message]
2017-07-21 13:29 ` Pankaj Gupta
2017-07-21 13:29 ` Pankaj Gupta
2017-07-21 14:00 ` Rik van Riel
2017-07-21 14:00 ` [Qemu-devel] " Rik van Riel
2017-07-21 14:00 ` Rik van Riel
2017-07-21 15:58 ` Stefan Hajnoczi
2017-07-21 15:58 ` [Qemu-devel] " Stefan Hajnoczi
2017-07-22 19:34 ` Dan Williams
2017-07-22 19:34 ` [Qemu-devel] " Dan Williams
2017-07-22 19:34 ` Dan Williams
2017-07-23 14:04 ` Rik van Riel
2017-07-23 14:04 ` [Qemu-devel] " Rik van Riel
2017-07-23 14:04 ` Rik van Riel
2017-07-23 16:01 ` Dan Williams
2017-07-23 16:01 ` [Qemu-devel] " Dan Williams
2017-07-23 16:01 ` Dan Williams
2017-07-23 18:10 ` Rik van Riel
2017-07-23 18:10 ` [Qemu-devel] " Rik van Riel
2017-07-23 18:10 ` Rik van Riel
2017-07-23 20:10 ` Dan Williams
2017-07-23 20:10 ` [Qemu-devel] " Dan Williams
2017-07-23 20:10 ` Dan Williams
2017-07-24 10:23 ` Jan Kara
2017-07-24 10:23 ` [Qemu-devel] " Jan Kara
2017-07-24 10:23 ` Jan Kara
2017-07-24 12:06 ` Pankaj Gupta
2017-07-24 12:06 ` [Qemu-devel] " Pankaj Gupta
2017-07-24 12:06 ` Pankaj Gupta
2017-07-24 12:37 ` Jan Kara
2017-07-24 12:37 ` [Qemu-devel] " Jan Kara
2017-07-24 12:37 ` Jan Kara
2017-07-24 15:10 ` Dan Williams
2017-07-24 15:10 ` [Qemu-devel] " Dan Williams
2017-07-24 15:10 ` Dan Williams
2017-07-24 15:48 ` Jan Kara
2017-07-24 15:48 ` [Qemu-devel] " Jan Kara
2017-07-24 15:48 ` Jan Kara
2017-07-24 16:19 ` Dan Williams
2017-07-24 16:19 ` [Qemu-devel] " Dan Williams
2017-07-24 16:19 ` Dan Williams
2017-07-25 14:27 ` Pankaj Gupta
2017-07-25 14:27 ` [Qemu-devel] " Pankaj Gupta
2017-07-25 14:27 ` Pankaj Gupta
2017-07-25 14:46 ` Dan Williams
2017-07-25 14:46 ` [Qemu-devel] " Dan Williams
2017-07-25 14:46 ` Dan Williams
2017-07-25 20:59 ` Rik van Riel
2017-07-25 20:59 ` [Qemu-devel] " Rik van Riel
2017-07-26 13:47 ` Pankaj Gupta
2017-07-26 13:47 ` [Qemu-devel] " Pankaj Gupta
2017-07-26 13:47 ` Pankaj Gupta
2017-07-26 21:27 ` Rik van Riel
2017-07-26 21:27 ` [Qemu-devel] " Rik van Riel
2017-07-26 21:40 ` Dan Williams
2017-07-26 21:40 ` [Qemu-devel] " Dan Williams
2017-07-26 21:40 ` Dan Williams
2017-07-26 23:46 ` Rik van Riel
2017-07-26 23:46 ` [Qemu-devel] " Rik van Riel
2017-07-26 23:46 ` Rik van Riel
2017-07-27 0:54 ` Dan Williams
2017-07-27 0:54 ` [Qemu-devel] " Dan Williams
2017-07-27 0:54 ` Dan Williams
2017-10-31 7:13 ` Xiao Guangrong
2017-10-31 7:13 ` [Qemu-devel] " Xiao Guangrong
2017-10-31 7:13 ` Xiao Guangrong
2017-10-31 14:20 ` Dan Williams
2017-10-31 14:20 ` [Qemu-devel] " Dan Williams
2017-10-31 14:20 ` Dan Williams
2017-11-01 3:43 ` Xiao Guangrong
2017-11-01 3:43 ` [Qemu-devel] " Xiao Guangrong
2017-11-01 3:43 ` Xiao Guangrong
2017-11-01 4:25 ` Dan Williams
2017-11-01 4:25 ` [Qemu-devel] " Dan Williams
2017-11-01 4:25 ` Dan Williams
2017-11-01 6:46 ` Xiao Guangrong
2017-11-01 6:46 ` [Qemu-devel] " Xiao Guangrong
2017-11-01 6:46 ` Xiao Guangrong
2017-11-01 15:20 ` Dan Williams
2017-11-01 15:20 ` [Qemu-devel] " Dan Williams
2017-11-01 15:20 ` Dan Williams
2017-11-02 8:50 ` Xiao Guangrong
2017-11-02 8:50 ` [Qemu-devel] " Xiao Guangrong
2017-11-02 8:50 ` Xiao Guangrong
2017-11-02 16:30 ` Dan Williams
2017-11-02 16:30 ` [Qemu-devel] " Dan Williams
2017-11-02 16:30 ` Dan Williams
2017-11-03 6:21 ` Xiao Guangrong
2017-11-03 6:21 ` [Qemu-devel] " Xiao Guangrong
2017-11-03 6:21 ` Xiao Guangrong
2017-11-21 18:19 ` Rik van Riel
2017-11-21 18:19 ` [Qemu-devel] " Rik van Riel
2017-11-21 18:26 ` Dan Williams
2017-11-21 18:26 ` [Qemu-devel] " Dan Williams
2017-11-21 18:26 ` Dan Williams
2017-11-21 18:35 ` Rik van Riel
2017-11-21 18:35 ` [Qemu-devel] " Rik van Riel
2017-11-23 4:05 ` Xiao Guangrong
2017-11-23 4:05 ` [Qemu-devel] " Xiao Guangrong
2017-11-23 4:05 ` Xiao Guangrong
2017-11-23 16:14 ` Dan Williams
2017-11-23 16:14 ` [Qemu-devel] " Dan Williams
2017-11-23 16:14 ` Dan Williams
2017-11-23 16:28 ` Paolo Bonzini
2017-11-23 16:28 ` [Qemu-devel] " Paolo Bonzini
2017-11-23 16:28 ` Paolo Bonzini
2017-11-24 12:40 ` Pankaj Gupta
2017-11-24 12:40 ` [Qemu-devel] " Pankaj Gupta
2017-11-24 12:40 ` Pankaj Gupta
2017-11-24 12:44 ` Paolo Bonzini
2017-11-24 12:44 ` [Qemu-devel] " Paolo Bonzini
2017-11-24 12:44 ` Paolo Bonzini
2017-11-24 13:02 ` [Qemu-devel] " Pankaj Gupta
2017-11-24 13:02 ` Pankaj Gupta
2017-11-24 13:20 ` Paolo Bonzini
2017-11-24 13:20 ` Paolo Bonzini
2017-11-28 18:03 ` Dan Williams
2017-11-28 18:03 ` [Qemu-devel] " Dan Williams
2017-11-28 18:03 ` Dan Williams
2018-01-13 6:23 ` Pankaj Gupta
2018-01-13 6:23 ` [Qemu-devel] " Pankaj Gupta
2018-01-13 6:23 ` Pankaj Gupta
2018-01-17 16:17 ` Dan Williams
2018-01-17 16:17 ` [Qemu-devel] " Dan Williams
2018-01-17 16:17 ` Dan Williams
2018-01-17 17:31 ` Pankaj Gupta
2018-01-17 17:31 ` [Qemu-devel] " Pankaj Gupta
2018-01-17 17:31 ` Pankaj Gupta
2018-01-18 16:53 ` David Hildenbrand
2018-01-18 16:53 ` [Qemu-devel] " David Hildenbrand
2018-01-18 16:53 ` David Hildenbrand
2018-01-18 17:38 ` Dan Williams
2018-01-18 17:38 ` [Qemu-devel] " Dan Williams
2018-01-18 17:38 ` Dan Williams
2018-01-18 17:48 ` David Hildenbrand
2018-01-18 17:48 ` [Qemu-devel] " David Hildenbrand
2018-01-18 17:48 ` David Hildenbrand
2018-01-18 18:45 ` Dan Williams
2018-01-18 18:45 ` [Qemu-devel] " Dan Williams
2018-01-18 18:45 ` Dan Williams
2018-01-18 18:54 ` Pankaj Gupta
2018-01-18 18:54 ` [Qemu-devel] " Pankaj Gupta
2018-01-18 18:54 ` Pankaj Gupta
2018-01-18 18:59 ` Dan Williams
2018-01-18 18:59 ` [Qemu-devel] " Dan Williams
2018-01-18 18:59 ` Dan Williams
2018-01-18 19:36 ` Pankaj Gupta
2018-01-18 19:36 ` [Qemu-devel] " Pankaj Gupta
2018-01-18 19:36 ` Pankaj Gupta
2018-01-18 19:48 ` Dan Williams
2018-01-18 19:48 ` [Qemu-devel] " Dan Williams
2018-01-18 19:48 ` Dan Williams
2018-01-18 19:51 ` David Hildenbrand
2018-01-18 19:51 ` [Qemu-devel] " David Hildenbrand
2018-01-18 19:51 ` David Hildenbrand
2018-01-18 20:11 ` Dan Williams
2018-01-18 20:11 ` [Qemu-devel] " Dan Williams
2018-01-18 20:11 ` Dan Williams
2017-11-06 7:57 ` [Qemu-devel] " Pankaj Gupta
2017-11-06 7:57 ` Pankaj Gupta
2017-11-06 16:57 ` Dan Williams
2017-11-06 16:57 ` Dan Williams
2017-11-07 11:21 ` Pankaj Gupta
2017-11-07 11:21 ` Pankaj Gupta
2017-11-07 11:21 ` Pankaj Gupta
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=46101617.33460557.1500643755247.JavaMail.zimbra@redhat.com \
--to=pagupta@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-nvdimm@ml01.01.org \
--cc=nilal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@redhat.com \
--cc=stefanha@gmail.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 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.