From: Sam Eiderman <shmuel.eiderman@oracle.com>
To: kwolf@redhat.com, mreitz@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Cc: shmuel.eiderman@oracle.com, eyal.moscovici@oracle.com,
sagi.amit@oracle.com, karl.heubaum@oracle.com,
liran.alon@oracle.com, arbel.moshe@oracle.com
Subject: [Qemu-devel] [PATCH 0/3] qemu-img: rebase: Improve/optimize rebase operation
Date: Thu, 2 May 2019 11:50:26 +0300 [thread overview]
Message-ID: <20190502085029.30776-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.
WARNING: multiple messages have this Message-ID (diff)
From: Sam Eiderman <shmuel.eiderman@oracle.com>
To: kwolf@redhat.com, mreitz@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
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 0/3] qemu-img: rebase: Improve/optimize rebase operation
Date: Thu, 2 May 2019 11:50:26 +0300 [thread overview]
Message-ID: <20190502085029.30776-1-shmuel.eiderman@oracle.com> (raw)
Message-ID: <20190502085026.p9XUt9Sjhj2jxlBv6PNUHWrcZBKqwE2IGW2uXGJwH3A@z> (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.
next reply other threads:[~2019-05-02 8:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 8:50 Sam Eiderman [this message]
2019-05-02 8:50 ` [Qemu-devel] [PATCH 0/3] qemu-img: rebase: Improve/optimize rebase operation Sam Eiderman
2019-05-02 8:50 ` [Qemu-devel] [PATCH 1/3] qemu-img: rebase: Reuse parent BlockDriverState Sam Eiderman
2019-05-02 8:50 ` Sam Eiderman
2019-05-02 8:50 ` [Qemu-devel] [PATCH 2/3] qemu-img: rebase: Reduce reads on in-chain rebase Sam Eiderman
2019-05-02 8:50 ` Sam Eiderman
2019-05-02 8:50 ` [Qemu-devel] [PATCH 3/3] qemu-img: rebase: Reuse in-chain BlockDriverState Sam Eiderman
2019-05-02 8:50 ` Sam Eiderman
2019-05-02 13:58 ` [Qemu-devel] [PATCH v2 0/3] qemu-img: rebase: Improve/optimize rebase operation Sam Eiderman
2019-05-02 13:58 ` Sam Eiderman
2019-05-02 13:58 ` [Qemu-devel] [PATCH v2 1/3] qemu-img: rebase: Reuse parent BlockDriverState Sam Eiderman
2019-05-02 13:58 ` Sam Eiderman
2019-05-23 13:07 ` Max Reitz
2019-05-02 13:58 ` [Qemu-devel] [PATCH v2 2/3] qemu-img: rebase: Reduce reads on in-chain rebase Sam Eiderman
2019-05-02 13:58 ` Sam Eiderman
2019-05-23 14:01 ` Max Reitz
2019-05-23 14:09 ` Sam Eiderman
2019-05-23 14:26 ` Max Reitz
2019-05-23 15:37 ` Sam Eiderman
2019-05-02 13:58 ` [Qemu-devel] [PATCH v2 3/3] qemu-img: rebase: Reuse in-chain BlockDriverState Sam Eiderman
2019-05-02 13:58 ` Sam Eiderman
2019-05-23 14:04 ` Max Reitz
2019-05-02 14:21 ` [Qemu-devel] [PATCH v2 0/3] qemu-img: rebase: Improve/optimize rebase operation Eric Blake
2019-05-02 14:21 ` Eric Blake
2019-05-02 14:38 ` Sam
2019-05-02 14:38 ` Sam
2019-05-19 8:34 ` Sam Eiderman
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=20190502085029.30776-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 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).