[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v5 0/2] Skip copy-on-write when allocating a zero cluster
From: |
Alberto Garcia |
Subject: |
[PATCH v5 0/2] Skip copy-on-write when allocating a zero cluster |
Date: |
Mon, 26 Oct 2020 17:58:25 +0100 |
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
- [PATCH v5 0/2] Skip copy-on-write when allocating a zero cluster,
Alberto Garcia <=