From: Alberto Garcia <berto@igalia.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PATCH v5 0/2] Skip copy-on-write when allocating a zero cluster
Date: Mon, 26 Oct 2020 17:58:25 +0100 [thread overview]
Message-ID: <cover.1603731354.git.berto@igalia.com> (raw)
I had to rebase the series due to conflicting changes on master. There
are no other differences.
Berto
v5:
- Fix rebase conflicts after 3555a43261
v4: https://lists.gnu.org/archive/html/qemu-block/2020-09/msg01515.html
- Fix rebase conflicts after cb8503159a
v3: https://lists.gnu.org/archive/html/qemu-block/2020-09/msg00912.html
- Add a new patch to improve the reporting of BDRV_BLOCK_ZERO [Vladimir]
- Rename function to bdrv_co_is_zero_fast() [Vladimir, Kevin]
- Don't call bdrv_common_block_status_above() if bytes == 0
v2: https://lists.gnu.org/archive/html/qemu-block/2020-08/msg01165.html
- Add new, simpler API: bdrv_is_unallocated_or_zero_above()
v1: https://lists.gnu.org/archive/html/qemu-block/2020-08/msg00403.html
Alberto Garcia (2):
qcow2: Report BDRV_BLOCK_ZERO more accurately in
bdrv_co_block_status()
qcow2: Skip copy-on-write when allocating a zero cluster
include/block/block.h | 2 ++
block/io.c | 35 +++++++++++++++++++++++++++++++----
block/qcow2.c | 35 +++++++++++++++++++----------------
3 files changed, 52 insertions(+), 20 deletions(-)
--
2.20.1
next reply other threads:[~2020-10-26 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 16:58 Alberto Garcia [this message]
2020-10-26 16:58 ` [PATCH v5 1/2] qcow2: Report BDRV_BLOCK_ZERO more accurately in bdrv_co_block_status() Alberto Garcia
2020-10-26 16:58 ` [PATCH v5 2/2] qcow2: Skip copy-on-write when allocating a zero cluster Alberto Garcia
2020-10-27 11:07 ` [PATCH v5 0/2] " Kevin Wolf
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=cover.1603731354.git.berto@igalia.com \
--to=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 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).