From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qcow2: Save another common flush
Date: Fri, 17 Sep 2010 12:05:04 -0500 [thread overview]
Message-ID: <4C939FC0.3000103@codemonkey.ws> (raw)
In-Reply-To: <1284740318-20838-1-git-send-email-kwolf@redhat.com>
On 09/17/2010 11:18 AM, Kevin Wolf wrote:
> For copy on write (this includes any cluster allocations that don't fill the
> whole cluster with one request), what qcow2 does looks like this:
>
> 1. Allocate new clusters (increase refcounts)
> 2. bdrv_flush
> 3. Copy sectors before the first touched one
> 4. bdrv_flush
> 5. Copy sectors after the last touched one
> 6. bdrv_flush
> 7. Update the L2 table to point to the new clusters
>
> Step 2 and 4 are not necessary. This series moves flushes around to get all
> of these three bdrv_flush calls merged into one.
>
Makes sense to me.
Regards,
Anthony Liguori
> Kevin Wolf (4):
> qcow2: Move sync out of write_refcount_block_entries
> qcow2: Move sync out of update_refcount
> qcow2: Move sync out of qcow2_alloc_clusters
> qcow2: Get rid of additional sync on COW
>
> block/qcow2-cluster.c | 11 ++++++++++-
> block/qcow2-refcount.c | 13 ++++++++++++-
> block/qcow2-snapshot.c | 2 ++
> 3 files changed, 24 insertions(+), 2 deletions(-)
>
>
prev parent reply other threads:[~2010-09-17 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 16:18 [Qemu-devel] [PATCH 0/4] qcow2: Save another common flush Kevin Wolf
2010-09-17 16:18 ` [Qemu-devel] [PATCH 1/4] qcow2: Move sync out of write_refcount_block_entries Kevin Wolf
2010-09-17 16:18 ` [Qemu-devel] [PATCH 2/4] qcow2: Move sync out of update_refcount Kevin Wolf
2010-09-17 17:06 ` Anthony Liguori
2010-09-17 17:19 ` Kevin Wolf
2010-09-17 16:18 ` [Qemu-devel] [PATCH 3/4] qcow2: Move sync out of qcow2_alloc_clusters Kevin Wolf
2010-09-17 16:18 ` [Qemu-devel] [PATCH 4/4] qcow2: Get rid of additional sync on COW Kevin Wolf
2010-09-17 17:05 ` Anthony Liguori [this message]
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=4C939FC0.3000103@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.