From: Eric Blake <eblake@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Denis Plotnikov <dplotnikov@virtuozzo.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 4/5] block, migration: add bdrv_flush_vmstate helper
Date: Tue, 16 Jun 2020 16:11:11 -0500 [thread overview]
Message-ID: <091af0f5-c8e9-8749-c329-287fb100f2b6@redhat.com> (raw)
In-Reply-To: <20200616162035.29857-5-den@openvz.org>
On 6/16/20 11:20 AM, Denis V. Lunev wrote:
> Right now bdrv_fclose() is just calling bdrv_flush().
>
> The problem is that migration code is working inefficently from black
inefficiently, block
> layer terms and are frequently called for very small pieces of not
> properly aligned data. Block layer is capable to work this way, but
s/not properly aligned/unaligned/
> this is very slow.
>
> This patch is a preparation for the introduction of the intermediate
> buffer at block driver state. It would be beneficial to separate
> conventional bdrv_flush() from closing QEMU file from migration code.
>
> The patch also forces bdrv_flush_vmstate() operation inside
> synchronous blk_save_vmstate() operation. This helper is used from
> qemu-io only.
>
> +++ b/block/block-backend.c
> @@ -2177,16 +2177,20 @@ int blk_truncate(BlockBackend *blk, int64_t offset, bool exact,
> int blk_save_vmstate(BlockBackend *blk, const uint8_t *buf,
> int64_t pos, int size)
> {
> - int ret;
> + int ret, ret2;
>
> if (!blk_is_available(blk)) {
> return -ENOMEDIUM;
> }
>
> ret = bdrv_save_vmstate(blk_bs(blk), buf, pos, size);
> + ret2 = bdrv_flush_vmstate(blk_bs(blk));
Do you really want to be attempting bdrv_flush_vmstate() even after
bdrv_save_vmstate() failed? Better might be...
> if (ret < 0) {
> return ret;
> }
...attempting it here, at which point it looks like the only reason you
need ret2 is to preserve ret long enough...
> + if (ret2 < 0) {
> + return ret2;
> + }
>
> if (ret == size && !blk->enable_write_cache) {
...for this check. But a quick look at bdrv_save_vmstate() says this
check is dead: the function can only return negative error or exactly
size, and we already filtered out negative error above.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-06-16 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 16:20 [PATCH v4 0/4] block: seriously improve savevm performance Denis V. Lunev
2020-06-16 16:20 ` [PATCH 1/5] migration/savevm: respect qemu_fclose() error code in save_snapshot() Denis V. Lunev
2020-06-16 16:20 ` [PATCH 2/5] block/aio_task: allow start/wait task from any coroutine Denis V. Lunev
2020-06-18 9:41 ` Vladimir Sementsov-Ogievskiy
2020-06-16 16:20 ` [PATCH 3/5] block/aio_task: drop aio_task_pool_wait_one() helper Denis V. Lunev
2020-06-18 9:41 ` Vladimir Sementsov-Ogievskiy
2020-06-16 16:20 ` [PATCH 4/5] block, migration: add bdrv_flush_vmstate helper Denis V. Lunev
2020-06-16 21:11 ` Eric Blake [this message]
2020-06-16 21:29 ` Denis V. Lunev
2020-06-18 10:03 ` Vladimir Sementsov-Ogievskiy
2020-06-18 10:02 ` Vladimir Sementsov-Ogievskiy
2020-06-16 16:20 ` [PATCH 5/5] block/io: improve savevm performance Denis V. Lunev
2020-06-18 10:56 ` Vladimir Sementsov-Ogievskiy
2020-06-18 11:07 ` Denis V. Lunev
2020-06-16 20:28 ` [PATCH v4 0/4] block: seriously " no-reply
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=091af0f5-c8e9-8749-c329-287fb100f2b6@redhat.com \
--to=eblake@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=dplotnikov@virtuozzo.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).