qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, jcody@redhat.com,
	Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/9] block: add differential backup support
Date: Tue, 23 Jun 2015 13:00:44 -0400	[thread overview]
Message-ID: <558990BC.2070605@redhat.com> (raw)
In-Reply-To: <1433463642-21840-1-git-send-email-jsnow@redhat.com>

Ping.

(Oh, I forgot to CC Stefan originally. :\)

Stefan: I know you said this wasn't expressly requisite, but I was
encouraged by Kevin to send it out as a usability patch for non-libvirt
users, so here it is.

Final "Yeah sure" or "No, definitely not" as 2.4 approaches?

Also note that if the answer is "Ehhh, maybe not now, nobody's REALLY
asked for it" we should still probably merge the first patch alone,
before our API solidifies -- this will give us the breathing room to add
these features in later if we want.

Thank you,
--John

(Oh, also note that this IS based on the now deprecated transactional
series I wrote, but if there is some use I can likely rebase without
much of a fuss on top of the BlockJobTxn approach.)


On 06/04/2015 08:20 PM, John Snow wrote:
> Requires: 1433454372-16356-1-git-send-email-jsnow@redhat.com
>           [0/10] block: incremental backup transactions
> 
> It's entirely possible to use the incremental backup primitives to
> achieve a differential backup mechanism, but in the interest of
> ease of use, I am proposing the explicit addition of the mechanism
> because it does not particularly complicate the code, add new edge
> cases, or present itself as difficult to test.
> 
> This series actually adds two ease of use features:
> 
> (1) Add a copy primitive for bitmaps to add flexibility to the
>     backup system in case users would like to later run multiple
>     backup chains (weekly vs. monthly or perhaps incremental vs.
>     differential)
> 
> (2) Add a 'differential' backup mode that does what the name says
>     on the tin.
> 
> ==
> For convenience, this branch is available at:
> https://github.com/jnsnow/qemu.git branch differential-backup
> https://github.com/jnsnow/qemu/tree/differential-backup
> 
> This version is tagged differential-backup-v1:
> https://github.com/jnsnow/qemu/releases/tag/differential-backup-v1
> ==
> 
> John Snow (9):
>   qapi: Rename 'dirty-bitmap' mode to 'incremental'
>   hbitmap: add hbitmap_copy
>   block: add bdrv_copy_dirty_bitmap
>   qapi: add Copy data type for bitmaps
>   qmp: add qmp cmd block-dirty-bitmap-copy
>   qmp: add block-dirty-bitmap-copy transaction
>   block: add differential backup mode
>   iotests: 124: support differential backups
>   iotests: add differential backup test
> 
>  block.c                    | 35 +++++++++++++++++-
>  block/backup.c             | 19 ++++++----
>  block/mirror.c             |  9 ++++-
>  blockdev.c                 | 61 +++++++++++++++++++++++++++++++
>  docs/bitmaps.md            |  8 ++--
>  include/block/block.h      |  5 +++
>  include/block/block_int.h  |  2 +-
>  include/qemu/hbitmap.h     |  9 +++++
>  qapi-schema.json           |  4 +-
>  qapi/block-core.json       | 40 ++++++++++++++++++--
>  qmp-commands.hx            | 36 ++++++++++++++++--
>  tests/qemu-iotests/124     | 91 +++++++++++++++++++++++++++++-----------------
>  tests/qemu-iotests/124.out |  4 +-
>  util/hbitmap.c             | 17 +++++++++
>  14 files changed, 280 insertions(+), 60 deletions(-)
> 

-- 
—js

  parent reply	other threads:[~2015-06-23 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05  0:20 [Qemu-devel] [PATCH 0/9] block: add differential backup support John Snow
2015-06-05  0:20 ` [Qemu-devel] [PATCH 1/9] qapi: Rename 'dirty-bitmap' mode to 'incremental' John Snow
2015-06-05  2:34   ` Eric Blake
2015-06-25 16:16   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-06-05  0:20 ` [Qemu-devel] [PATCH 2/9] hbitmap: add hbitmap_copy John Snow
2015-06-05  2:37   ` Eric Blake
2015-06-05  0:20 ` [Qemu-devel] [PATCH 3/9] block: add bdrv_copy_dirty_bitmap John Snow
2015-06-05  2:42   ` Eric Blake
2015-06-05  0:20 ` [Qemu-devel] [PATCH 4/9] qapi: add Copy data type for bitmaps John Snow
2015-06-05  2:57   ` Eric Blake
2015-06-05  0:20 ` [Qemu-devel] [PATCH 5/9] qmp: add qmp cmd block-dirty-bitmap-copy John Snow
2015-06-05  3:04   ` Eric Blake
2015-06-05  0:20 ` [Qemu-devel] [PATCH 6/9] qmp: add block-dirty-bitmap-copy transaction John Snow
2015-06-05  0:20 ` [Qemu-devel] [PATCH 7/9] block: add differential backup mode John Snow
2015-06-05  0:20 ` [Qemu-devel] [PATCH 8/9] iotests: 124: support differential backups John Snow
2015-06-05  0:20 ` [Qemu-devel] [PATCH 9/9] iotests: add differential backup test John Snow
2015-06-23 17:00 ` John Snow [this message]
2015-06-24 14:33   ` [Qemu-devel] [PATCH 0/9] block: add differential backup support Stefan Hajnoczi

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=558990BC.2070605@redhat.com \
    --to=jsnow@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@parallels.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).