From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: mreitz@redhat.com, kwolf@redhat.com, berto@igalia.com,
pbonzini@redhat.com, vsementsov@virtuozzo.com, den@openvz.org,
berrange@redhat.com
Subject: [Qemu-devel] [PATCH v4 7/9] qcow2: qcow2_co_preadv: skip using hd_qiov when possible
Date: Mon, 11 Feb 2019 17:44:19 +0300 [thread overview]
Message-ID: <20190211144421.106232-8-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20190211144421.106232-1-vsementsov@virtuozzo.com>
qemu_iovec_memset has @offset parameter, so using hd_qiov for it is not
needed.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
---
block/qcow2.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 29be900555..3f39ec0c05 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -1888,16 +1888,11 @@ static coroutine_fn int qcow2_co_preadv(BlockDriverState *bs, uint64_t offset,
goto fail;
}
- offset_in_cluster = offset_into_cluster(s, offset);
-
- qemu_iovec_reset(&hd_qiov);
- qemu_iovec_concat(&hd_qiov, qiov, bytes_done, cur_bytes);
-
if (ret == QCOW2_CLUSTER_ZERO_PLAIN ||
ret == QCOW2_CLUSTER_ZERO_ALLOC ||
(ret == QCOW2_CLUSTER_UNALLOCATED && !bs->backing))
{
- qemu_iovec_memset(&hd_qiov, 0, 0, cur_bytes);
+ qemu_iovec_memset(qiov, bytes_done, 0, cur_bytes);
bytes -= cur_bytes;
offset += cur_bytes;
@@ -1905,6 +1900,11 @@ static coroutine_fn int qcow2_co_preadv(BlockDriverState *bs, uint64_t offset,
continue;
}
+ offset_in_cluster = offset_into_cluster(s, offset);
+
+ qemu_iovec_reset(&hd_qiov);
+ qemu_iovec_concat(&hd_qiov, qiov, bytes_done, cur_bytes);
+
qemu_co_mutex_unlock(&s->lock);
switch (ret) {
--
2.18.0
next prev parent reply other threads:[~2019-02-11 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 14:44 [Qemu-devel] [PATCH v4 0/9] qcow2: encryption threads Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 1/9] qcow2.h: add missing include Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 2/9] qcow2: add separate file for threaded data processing functions Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 3/9] qcow2-threads: use thread_pool_submit_co Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 4/9] qcow2-threads: qcow2_co_do_compress: protect queuing by mutex Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 5/9] qcow2-threads: split out generic path Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 6/9] qcow2: qcow2_co_preadv: improve locking Vladimir Sementsov-Ogievskiy
2019-02-11 14:44 ` Vladimir Sementsov-Ogievskiy [this message]
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 8/9] qcow2: bdrv_co_pwritev: move encryption code out of the lock Vladimir Sementsov-Ogievskiy
2019-02-11 15:27 ` Alberto Garcia
2019-02-11 14:44 ` [Qemu-devel] [PATCH v4 9/9] qcow2: do encryption in threads Vladimir Sementsov-Ogievskiy
2019-02-27 9:56 ` [Qemu-devel] [PATCH v4 0/9] qcow2: encryption threads Vladimir Sementsov-Ogievskiy
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=20190211144421.106232-8-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).