All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org, famz@redhat.com,
	kwolf@redhat.com, mreitz@redhat.com, stefanha@redhat.com,
	den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v2 0/5] backup improvements part 1
Date: Tue, 28 Nov 2017 14:44:13 -0500	[thread overview]
Message-ID: <20171128194413.GJ25110@localhost.localdomain> (raw)
In-Reply-To: <20171114050006.GD5399@localhost.localdomain>

On Tue, Nov 14, 2017 at 12:00:06AM -0500, Jeff Cody wrote:
> On Mon, Nov 13, 2017 at 05:41:13PM -0500, John Snow wrote:
> > Jeff, I think this ought to go through your tree, but I'll sign off on it.
> > 
> > Fam: Do you agree?
> > 
> > (Probably -next material, but I'm sending this email because I'm taking
> > it out of my review queue and I don't want it to get lost.)
> > 
> > --js
> > 
> 
> Yes, I can bring in through my tree, unless Fam prefers to have it - I'll
> pull it in via my block-next branch.
> 

Rather than keep this on my email queue:

Applied to my block-next branch:

git://github.com/codyprime/qemu-kvm-jtc block-next

-Jeff
> 
> > On 10/12/2017 09:53 AM, Vladimir Sementsov-Ogievskiy wrote:
> > > Hi all. Here is a continuation of my "new backup architecture" series,
> > > The very first part, but it is meaningful itself.
> > > 
> > > v2: rebase on master
> > > 01: add test and fix bug
> > > 02: move commit about NONE mode to this patch, add John's r-b (hope,
> > >      you are OK with this tiny change)
> > > 03: tiny refactor (John)
> > > 04: improve commit message, add John's r-b
> > > 05: add John's r-b
> > > 
> > > Vladimir Sementsov-Ogievskiy (5):
> > >   hbitmap: add next_zero function
> > >   backup: move from done_bitmap to copy_bitmap
> > >   backup: init copy_bitmap from sync_bitmap for incremental
> > >   backup: simplify non-dirty bits progress processing
> > >   backup: use copy_bitmap in incremental backup
> > > 
> > >  include/block/dirty-bitmap.h |   1 +
> > >  include/qemu/hbitmap.h       |   8 +++
> > >  block/backup.c               | 118 ++++++++++++++++++++++++-------------------
> > >  block/dirty-bitmap.c         |   5 ++
> > >  tests/test-hbitmap.c         |  61 ++++++++++++++++++++++
> > >  util/hbitmap.c               |  39 ++++++++++++++
> > >  6 files changed, 180 insertions(+), 52 deletions(-)
> > > 

  reply	other threads:[~2017-11-28 19:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 13:53 [Qemu-devel] [PATCH v2 0/5] backup improvements part 1 Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 1/5] hbitmap: add next_zero function Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 2/5] backup: move from done_bitmap to copy_bitmap Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 3/5] backup: init copy_bitmap from sync_bitmap for incremental Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 4/5] backup: simplify non-dirty bits progress processing Vladimir Sementsov-Ogievskiy
2017-10-12 13:53 ` [Qemu-devel] [PATCH 5/5] backup: use copy_bitmap in incremental backup Vladimir Sementsov-Ogievskiy
2017-10-12 14:31 ` [Qemu-devel] [PATCH v2 0/5] backup improvements part 1 no-reply
2017-10-13  7:37   ` Vladimir Sementsov-Ogievskiy
2017-10-13 13:15     ` [Qemu-devel] iotest 77 failure [was: [PATCH v2 0/5] backup improvements part 1] Eric Blake
2017-10-31 10:26 ` [Qemu-devel] ping Re: [PATCH v2 0/5] backup improvements part 1 Vladimir Sementsov-Ogievskiy
2017-11-02 20:52   ` John Snow
2017-11-03  5:37     ` Vladimir Sementsov-Ogievskiy
2017-11-07  0:26 ` [Qemu-devel] " John Snow
2017-11-13 22:41 ` John Snow
2017-11-14  5:00   ` Jeff Cody
2017-11-28 19:44     ` Jeff Cody [this message]
2017-11-29  1:27       ` Fam Zheng
2017-11-29  1:26   ` Fam Zheng

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=20171128194413.GJ25110@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=den@openvz.org \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.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.