[v4] Skip copy-on-write when allocating a zero cluster

[PATCH v4 0/2] Skip copy-on-write when allocating a zero cluster

Alberto Garcia posted 2 patches 3 years, 7 months ago

Diff against v3 v5
Download series mbox

Test docker-quick@centos7 passed

Test docker-mingw@fedora passed

Test checkpatch passed

Test FreeBSD passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/cover.1600698425.git.berto@igalia.com

Maintainers: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>, Fam Zheng <fam@euphon.net>, Stefan Hajnoczi <stefanha@redhat.com>

There is a newer version of this series

include/block/block.h |  2 ++
block/io.c            | 35 +++++++++++++++++++++++++++++++----
block/qcow2.c         | 35 +++++++++++++++++++----------------
3 files changed, 52 insertions(+), 20 deletions(-)

Expand all Fold all

[PATCH v4 0/2] Skip copy-on-write when allocating a zero cluster

Posted by Alberto Garcia 3 years, 7 months ago

I had to rebase the series due to conflicting changes on master. There
are no other differences.

Berto

v4:
- 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

Re: [PATCH v4 0/2] Skip copy-on-write when allocating a zero cluster

Posted by Alberto Garcia 3 years, 6 months ago

ping

On Mon 21 Sep 2020 04:30:48 PM CEST, Alberto Garcia wrote:
> I had to rebase the series due to conflicting changes on master. There
> are no other differences.
>
> Berto
>
> v4:
> - 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