From: "Denis V. Lunev" <den@openvz.org>
To: qemu-devel@nongnu.org
Cc: den@openvz.org, Eric Blake <eblake@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/5] qcow2_co_write_zeroes and related improvements
Date: Tue, 17 May 2016 12:15:38 +0300 [thread overview]
Message-ID: <1463476543-3087-1-git-send-email-den@openvz.org> (raw)
This series enables tracepoints in qemu-io and improves
bdrv/qcow2_co_write_zeroes framework.
Signed-off-by: Denis V. Lunev <den@openvz.org>
CC: Eric Blake <eblake@redhat.com>
CC: Kevin Wolf <kwolf@redhat.com>
Changes from v1:
- patch 1 is separated to additional patchset
- grammar fixes, thank you Eric
Denis V. Lunev (5):
block: split write_zeroes always
qcow2: simplify logic in qcow2_co_write_zeroes
qcow2: add tracepoints for qcow2_co_write_zeroes
qcow2: fix condition in is_zero_cluster
qcow2: merge is_zero_cluster helpers into qcow2_co_write_zeroes
block/io.c | 6 +++---
block/qcow2.c | 63 ++++++++++++++++++++++-------------------------------------
trace-events | 2 ++
3 files changed, 28 insertions(+), 43 deletions(-)
--
2.1.4
next reply other threads:[~2016-05-17 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 9:15 Denis V. Lunev [this message]
2016-05-17 9:15 ` [Qemu-devel] [PATCH 1/5] block: split write_zeroes always Denis V. Lunev
2016-05-17 16:34 ` Kevin Wolf
2016-05-25 18:36 ` Eric Blake
2016-05-17 9:15 ` [Qemu-devel] [PATCH 2/5] qcow2: simplify logic in qcow2_co_write_zeroes Denis V. Lunev
2016-05-17 9:15 ` [Qemu-devel] [PATCH 3/5] qcow2: add tracepoints for qcow2_co_write_zeroes Denis V. Lunev
2016-05-17 15:37 ` Eric Blake
2016-05-17 9:15 ` [Qemu-devel] [PATCH 4/5] qcow2: fix condition in is_zero_cluster Denis V. Lunev
2016-05-17 15:11 ` Kevin Wolf
2016-05-17 9:15 ` [Qemu-devel] [PATCH 5/5] qcow2: merge is_zero_cluster helpers into qcow2_co_write_zeroes Denis V. Lunev
2016-05-24 18:14 ` Eric Blake
2016-05-17 15:11 ` [Qemu-devel] [PATCH v2 0/5] qcow2_co_write_zeroes and related improvements Kevin Wolf
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=1463476543-3087-1-git-send-email-den@openvz.org \
--to=den@openvz.org \
--cc=eblake@redhat.com \
--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 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).