From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, hbrock@redhat.com, qemu-devel@nongnu.org,
rjones@redhat.com, imain@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 00/11] Point-in-time snapshot exporting over NBD
Date: Tue, 23 Jul 2013 09:52:48 +0800 [thread overview]
Message-ID: <51EDE1F0.9010705@linux.vnet.ibm.com> (raw)
In-Reply-To: <51E917F7.9000308@linux.vnet.ibm.com>
于 2013-7-19 18:41, Wenchao Xia 写道:
> 于 2013-7-17 17:42, Fam Zheng 写道:
>> This series adds for point-in-time snapshot NBD exporting based on
>> blockdev-backup (variant of drive-backup with existing device as target). This
>> patch is built on top of imain's sync mode patches for drive-backup.
>>
>> We get a thin point-in-time snapshot by COW mechanism of drive-backup, and
>> export it through built in NBD server. The steps are as below:
>>
> Compared with driver-backup, this approach is more flexible in some way,
> since user can read the content and copy out what he need, with a
> sacrifice of write of old data to temporary file. Overall it seems good.
>
> Dirty change tracking is what miss for a full solution, which
> naturally exist in backing chain snapshot.
>
>>
>
>
Any one is doing dirty tracking feature? If no, I'd like to draft a
version based on add-cow.
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-07-23 1:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 9:42 [Qemu-devel] [PATCH v2 00/11] Point-in-time snapshot exporting over NBD Fam Zheng
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 01/11] block: replace in_use with refcnt_soft and refcnt_hard Fam Zheng
2013-07-17 12:26 ` Paolo Bonzini
2013-07-18 4:53 ` Fam Zheng
2013-07-23 9:36 ` Stefan Hajnoczi
2013-07-23 10:32 ` Fam Zheng
2013-07-23 13:34 ` Stefan Hajnoczi
2013-07-24 0:39 ` Fam Zheng
2013-07-24 7:35 ` Stefan Hajnoczi
2013-07-24 7:44 ` Fam Zheng
2013-07-25 7:52 ` Stefan Hajnoczi
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 02/11] block: use refcnt for bs->backing_hd and bs->file Fam Zheng
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 03/11] block: use refcnt for drive_init/drive_uninit Fam Zheng
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 04/11] block: use refcnt for device attach/detach Fam Zheng
2013-07-23 9:44 ` Stefan Hajnoczi
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 05/11] migration: omit drive ref as we have bdrv_ref now Fam Zheng
2013-07-23 9:49 ` Stefan Hajnoczi
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 06/11] xen_disk: simplify blk_disconnect with refcnt Fam Zheng
2013-07-23 9:50 ` Stefan Hajnoczi
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 07/11] block: hold hard reference for backup/mirror target Fam Zheng
2013-07-23 9:52 ` Stefan Hajnoczi
2013-07-25 6:08 ` Fam Zheng
2013-07-25 7:59 ` Stefan Hajnoczi
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 08/11] block: simplify bdrv_drop_intermediate Fam Zheng
2013-07-24 23:16 ` Jeff Cody
2013-07-25 1:34 ` Fam Zheng
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 09/11] block: add assertion to check refcount before deleting Fam Zheng
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 10/11] block: add option 'backing' to -drive options Fam Zheng
2013-07-17 12:36 ` Paolo Bonzini
2013-07-17 12:58 ` Kevin Wolf
2013-07-17 13:13 ` Paolo Bonzini
2013-07-17 13:48 ` Kevin Wolf
2013-07-17 14:16 ` Paolo Bonzini
2013-07-17 15:09 ` Kevin Wolf
2013-07-17 15:23 ` Paolo Bonzini
2013-07-23 20:07 ` Ian Main
2013-07-22 6:07 ` Fam Zheng
2013-07-23 19:57 ` Ian Main
2013-07-17 9:42 ` [Qemu-devel] [PATCH v2 11/11] qmp: add command 'blockdev-backup' Fam Zheng
2013-07-17 12:44 ` Eric Blake
2013-07-18 4:41 ` Fam Zheng
2013-07-19 10:16 ` Wenchao Xia
2013-07-23 10:10 ` Stefan Hajnoczi
2013-07-19 10:41 ` [Qemu-devel] [PATCH v2 00/11] Point-in-time snapshot exporting over NBD Wenchao Xia
2013-07-23 1:52 ` Wenchao Xia [this message]
2013-07-23 6:35 ` Paolo Bonzini
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=51EDE1F0.9010705@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=famz@redhat.com \
--cc=hbrock@redhat.com \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@redhat.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).