From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>, Eric Blake <eblake@redhat.com>,
"Denis V . Lunev" <den@openvz.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/7] Reduce the number of I/O ops when doing COW
Date: Tue, 20 Jun 2017 16:32:24 +0200 [thread overview]
Message-ID: <20170620143224.GB6306@noname.redhat.com> (raw)
In-Reply-To: <cover.1497879398.git.berto@igalia.com>
Am 19.06.2017 um 15:40 hat Alberto Garcia geschrieben:
> Hi all,
>
> here's a patch series that rewrites the copy-on-write code in the
> qcow2 driver to reduce the number of I/O operations.
>
> This is version v4, please refer to the original e-mail for a complete
> description:
>
> https://lists.gnu.org/archive/html/qemu-block/2017-05/msg00882.html
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2017-06-20 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 13:40 [Qemu-devel] [PATCH v4 0/7] Reduce the number of I/O ops when doing COW Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 1/7] qcow2: Remove unused Error variable in do_perform_cow() Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 2/7] qcow2: Use unsigned int for both members of Qcow2COWRegion Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 3/7] qcow2: Make perform_cow() call do_perform_cow() twice Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 4/7] qcow2: Split do_perform_cow() into _read(), _encrypt() and _write() Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 5/7] qcow2: Allow reading both COW regions with only one request Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 6/7] qcow2: Pass a QEMUIOVector to do_perform_cow_{read, write}() Alberto Garcia
2017-06-19 13:40 ` [Qemu-devel] [PATCH v4 7/7] qcow2: Merge the writing of the COW regions with the guest data Alberto Garcia
2017-06-20 14:32 ` Kevin Wolf [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=20170620143224.GB6306@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).