From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/7] block/qcow2: Improve zero cluster expansion
Date: Fri, 15 Aug 2014 17:47:01 +0200 [thread overview]
Message-ID: <1408117628-17512-1-git-send-email-mreitz@redhat.com> (raw)
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).
This series depends on v2 of my "qemu-img: Allow source cache mode
specification" series.
Changes from v2:
- Patch 1: Fixed misspelling in the commit message [Eric]
git-backport-diff against v2:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/7:[----] [--] 'block: Add status callback to bdrv_amend_options()'
002/7:[----] [--] 'qemu-img: Add progress output for amend'
003/7:[----] [--] 'qemu-img: Fix insignificant memleak'
004/7:[----] [--] 'block/qcow2: Implement status CB for amend'
005/7:[----] [--] 'block/qcow2: Make get_refcount() global'
006/7:[----] [--] 'block/qcow2: Simplify shared L2 handling in amend'
007/7:[----] [--] 'iotests: Expand test 061'
Max Reitz (7):
block: Add status callback to bdrv_amend_options()
qemu-img: Add progress output for amend
qemu-img: Fix insignificant memleak
block/qcow2: Implement status CB for amend
block/qcow2: Make get_refcount() global
block/qcow2: Simplify shared L2 handling in amend
iotests: Expand test 061
block.c | 5 +-
block/qcow2-cluster.c | 115 ++++++++++++++++++++++-----------------------
block/qcow2-refcount.c | 26 +++++-----
block/qcow2.c | 10 ++--
block/qcow2.h | 5 +-
include/block/block.h | 8 +++-
include/block/block_int.h | 3 +-
qemu-img-cmds.hx | 4 +-
qemu-img.c | 29 ++++++++++--
qemu-img.texi | 2 +-
tests/qemu-iotests/061 | 25 ++++++++++
tests/qemu-iotests/061.out | 30 ++++++++++++
tests/qemu-iotests/group | 2 +-
13 files changed, 174 insertions(+), 90 deletions(-)
--
2.0.3
next reply other threads:[~2014-08-15 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 15:47 Max Reitz [this message]
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 1/7] block: Add status callback to bdrv_amend_options() Max Reitz
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 2/7] qemu-img: Add progress output for amend Max Reitz
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 3/7] qemu-img: Fix insignificant memleak Max Reitz
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 4/7] block/qcow2: Implement status CB for amend Max Reitz
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 5/7] block/qcow2: Make get_refcount() global Max Reitz
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 6/7] block/qcow2: Simplify shared L2 handling in amend Max Reitz
2014-08-15 15:47 ` [Qemu-devel] [PATCH v3 7/7] iotests: Expand test 061 Max Reitz
2014-10-08 19:48 ` [Qemu-devel] [PATCH v3 0/7] block/qcow2: Improve zero cluster expansion Max Reitz
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=1408117628-17512-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).