From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/7] block/qcow2: Improve zero cluster expansion
Date: Tue, 28 Oct 2014 17:39:12 +0100 [thread overview]
Message-ID: <20141028163912.GF4828@noname.str.redhat.com> (raw)
In-Reply-To: <1414404776-4919-1-git-send-email-mreitz@redhat.com>
Am 27.10.2014 um 11:12 hat Max Reitz geschrieben:
> The main purpose of this series is to add a progress report to
> qemu-img amend. This is achieved by adding a callback function to
> bdrv_amend_options() - the reasons for this choice are explained in
> patch 1.
>
> While adapting qcow2's expand_zero_clusters_in_l1() accordingly, I
> noticed a way to simplify it and get rid of the rather ugly bitmap used
> there (patch 6).
Had a question on patch 7, but regardless:
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
next prev parent reply other threads:[~2014-10-28 16:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:12 [Qemu-devel] [PATCH v4 0/7] block/qcow2: Improve zero cluster expansion Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 1/7] block: Add status callback to bdrv_amend_options() Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 2/7] qemu-img: Add progress output for amend Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 3/7] qemu-img: Fix insignificant memleak Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 4/7] block/qcow2: Implement status CB for amend Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 5/7] block/qcow2: Make get_refcount() global Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 6/7] block/qcow2: Simplify shared L2 handling in amend Max Reitz
2014-10-27 10:12 ` [Qemu-devel] [PATCH v4 7/7] iotests: Expand test 061 Max Reitz
2014-10-28 16:38 ` Kevin Wolf
2014-10-28 16:47 ` Max Reitz
2014-10-28 16:39 ` Kevin Wolf [this message]
2014-10-29 10:37 ` [Qemu-devel] [PATCH v4 0/7] block/qcow2: Improve zero cluster expansion 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=20141028163912.GF4828@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).