From: Sam Eiderman <shmuel.eiderman@oracle.com>
To: kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
mreitz@redhat.com
Cc: eyal.moscovici@oracle.com, arbel.moshe@oracle.com,
liran.alon@oracle.com, shmuel.eiderman@oracle.com,
sagi.amit@oracle.com, karl.heubaum@oracle.com
Subject: [Qemu-devel] [PATCH v4 0/3] qemu-img: rebase: Improve/optimize rebase operation
Date: Thu, 23 May 2019 18:44:41 +0300 [thread overview]
Message-ID: <20190523154444.28783-1-shmuel.eiderman@oracle.com> (raw)
This patch series aims to improve the speed of qemu-img rebase.
1. Mainly by removing unnecessary reads when rebasing on the same
chain.
2. But also by minimizing the number of bdrv_open calls rebase
requires.
v2:
* Added missing g_free in
"qemu-img: rebase: Reuse in-chain BlockDriverState"
v3:
* Rebased on top of "Allow rebase with no input base" series
v4:
* Using backing_bs(bs) when a prefix was detected since bs was
already checked for allocation.
Sam Eiderman (3):
qemu-img: rebase: Reuse parent BlockDriverState
qemu-img: rebase: Reduce reads on in-chain rebase
qemu-img: rebase: Reuse in-chain BlockDriverState
qemu-img.c | 85 ++++++++++++++++++++++++++++++++++++++++----------------------
1 file changed, 55 insertions(+), 30 deletions(-)
--
2.13.3
next reply other threads:[~2019-05-23 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 15:44 Sam Eiderman [this message]
2019-05-23 15:44 ` [Qemu-devel] [PATCH v4 1/3] qemu-img: rebase: Reuse parent BlockDriverState Sam Eiderman
2019-05-23 16:13 ` Max Reitz
2019-05-23 15:44 ` [Qemu-devel] [PATCH v4 2/3] qemu-img: rebase: Reduce reads on in-chain rebase Sam Eiderman
2019-05-23 16:14 ` Max Reitz
2019-05-23 16:35 ` Sam Eiderman
2019-05-23 15:44 ` [Qemu-devel] [PATCH v4 3/3] qemu-img: rebase: Reuse in-chain BlockDriverState Sam Eiderman
2019-05-23 16:14 ` 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=20190523154444.28783-1-shmuel.eiderman@oracle.com \
--to=shmuel.eiderman@oracle.com \
--cc=arbel.moshe@oracle.com \
--cc=eyal.moscovici@oracle.com \
--cc=karl.heubaum@oracle.com \
--cc=kwolf@redhat.com \
--cc=liran.alon@oracle.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sagi.amit@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.