From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, wencongyang2@huawei.com,
xiechanglong.d@gmail.com, qemu-devel@nongnu.org,
armbru@redhat.com, den@openvz.org, jsnow@redhat.com
Subject: Re: [PATCH v3 19/25] backup: move to block-copy
Date: Tue, 12 Jan 2021 14:23:34 +0100 [thread overview]
Message-ID: <9708f8d8-3afc-f30d-9245-20071763c5a3@redhat.com> (raw)
In-Reply-To: <20201026171815.13233-20-vsementsov@virtuozzo.com>
On 26.10.20 18:18, Vladimir Sementsov-Ogievskiy wrote:
> This brings async request handling and block-status driven chunk sizes
> to backup out of the box, which improves backup performance.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> block/backup.c | 187 ++++++++++++++++++++++++++++++++-----------------
> 1 file changed, 121 insertions(+), 66 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
Irrelevant notes below.
> diff --git a/block/backup.c b/block/backup.c
> index 449b763ce4..0d1cd64eab 100644
> --- a/block/backup.c
> +++ b/block/backup.c
(Just something I noted when looking for remaining instances of
“ratelimit”: backup.c includes ratelimit.h, which I don’t think it needs
to do any longer)
[...]
> static int coroutine_fn backup_loop(BackupBlockJob *job)
> {
[...]
> + if (!block_copy_call_finished(s) &&
> + job_is_cancelled(&job->common.job))
> + {
Just for the sake of clarity: If !block_copy_call_finished(), then
job_is_cancelled() must be true, right?
(I.e., could be an assertion instead of the second part of the
condition. I don’t mind how it is, but then again, it did made me ask.)
> + /*
> + * Note that we can't use job_yield() here, as it doesn't work for
> + * cancelled job.
> + */
> + block_copy_call_cancel(s);
> + job->wait = true;
> + qemu_coroutine_yield();
> + assert(block_copy_call_finished(s));
> + ret = 0;
> + goto out;
> + }
> +
> + if (job_is_cancelled(&job->common.job) ||
> + block_copy_call_succeeded(s))
> + {
> + ret = 0;
> + goto out;
> + }
> +
> + if (block_copy_call_cancelled(s)) {
> + /*
> + * Job is not cancelled but only block-copy call. This is possible
> + * after job pause. Now the pause is finished, start new block-copy
> + * iteration.
> + */
> + block_copy_call_free(s);
> + continue;
If one were to avoid all continues, we could alternatively put the whole
error handling into a block_copy_call_failed() condition, and have the
block_copy_call_free() common for both the cancel and the fail case.
*shrug*
> + }
> +
> + /* The only remaining case is failed block-copy call. */
> + assert(block_copy_call_failed(s));
> +
> + ret = block_copy_call_status(s, &error_is_read);
> + act = backup_error_action(job, error_is_read, -ret);
> + switch (act) {
> + case BLOCK_ERROR_ACTION_REPORT:
> + goto out;
> + case BLOCK_ERROR_ACTION_STOP:
> + /*
> + * Go to pause prior to starting new block-copy call on the next
> + * iteration.
> + */
> + job_pause_point(&job->common.job);
> + break;
> + case BLOCK_ERROR_ACTION_IGNORE:
> + /* Proceed to new block-copy call to retry. */
> + break;
> + default:
> + abort();
> + }
> +
> + block_copy_call_free(s);
> }
>
> - out:
> - bdrv_dirty_iter_free(bdbi);
> +out:
> + block_copy_call_free(s);
Reads a bit weird after the block_copy_call_free(s) at the end of the
while (true) loop, but is entirely correct, of course. (And I can’t
offer any better alternative.)
Max
> + job->bg_bcs_call = NULL;
> return ret;
> }
next prev parent reply other threads:[~2021-01-12 13:27 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 17:17 [PATCH v3 00/25] backup performance: block_status + async Vladimir Sementsov-Ogievskiy
2020-10-26 17:17 ` [PATCH v3 01/25] iotests: 129 don't check backup "busy" Vladimir Sementsov-Ogievskiy
2020-10-26 17:17 ` [PATCH v3 02/25] qapi: backup: add perf.use-copy-range parameter Vladimir Sementsov-Ogievskiy
2021-01-11 16:07 ` Max Reitz
2021-01-19 20:21 ` Eric Blake
2021-01-20 6:09 ` Vladimir Sementsov-Ogievskiy
2021-01-20 8:24 ` Max Reitz
2020-10-26 17:17 ` [PATCH v3 03/25] block/block-copy: More explicit call_state Vladimir Sementsov-Ogievskiy
2020-10-26 17:17 ` [PATCH v3 04/25] block/block-copy: implement block_copy_async Vladimir Sementsov-Ogievskiy
2021-01-11 16:27 ` Max Reitz
2020-10-26 17:17 ` [PATCH v3 05/25] block/block-copy: add max_chunk and max_workers parameters Vladimir Sementsov-Ogievskiy
2021-01-11 16:47 ` Max Reitz
2020-10-26 17:17 ` [PATCH v3 06/25] block/block-copy: add list of all call-states Vladimir Sementsov-Ogievskiy
2021-01-11 17:02 ` Max Reitz
2020-10-26 17:17 ` [PATCH v3 07/25] block/block-copy: add ratelimit to block-copy Vladimir Sementsov-Ogievskiy
2021-01-12 10:48 ` Max Reitz
2020-10-26 17:17 ` [PATCH v3 08/25] block/block-copy: add block_copy_cancel Vladimir Sementsov-Ogievskiy
2021-01-12 11:05 ` Max Reitz
2020-10-26 17:17 ` [PATCH v3 09/25] blockjob: add set_speed to BlockJobDriver Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 10/25] job: call job_enter from job_user_pause Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 11/25] qapi: backup: add max-chunk and max-workers to x-perf struct Vladimir Sementsov-Ogievskiy
2020-11-09 12:23 ` Vladimir Sementsov-Ogievskiy
2021-01-12 11:59 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 12/25] iotests: 56: prepare for backup over block-copy Vladimir Sementsov-Ogievskiy
2021-01-12 12:07 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 13/25] iotests: 129: " Vladimir Sementsov-Ogievskiy
2021-01-12 12:14 ` Max Reitz
2021-01-16 21:03 ` Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 14/25] iotests: 185: " Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 15/25] iotests: 219: " Vladimir Sementsov-Ogievskiy
2021-01-12 12:32 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 16/25] iotests: 257: " Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 17/25] block/block-copy: make progress_bytes_callback optional Vladimir Sementsov-Ogievskiy
2021-01-12 12:39 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 18/25] block/backup: drop extra gotos from backup_run() Vladimir Sementsov-Ogievskiy
2021-01-12 12:40 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 19/25] backup: move to block-copy Vladimir Sementsov-Ogievskiy
2021-01-12 13:23 ` Max Reitz [this message]
2021-01-12 15:27 ` Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 20/25] qapi: backup: disable copy_range by default Vladimir Sementsov-Ogievskiy
2021-01-12 14:05 ` Max Reitz
2021-01-12 15:44 ` Vladimir Sementsov-Ogievskiy
2021-01-12 15:55 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 21/25] block/block-copy: drop unused block_copy_set_progress_callback() Vladimir Sementsov-Ogievskiy
2021-01-12 14:07 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 22/25] block/block-copy: drop unused argument of block_copy() Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 23/25] simplebench/bench_block_job: use correct shebang line with python3 Vladimir Sementsov-Ogievskiy
2021-01-12 14:10 ` Max Reitz
2020-10-26 17:18 ` [PATCH v3 24/25] simplebench: bench_block_job: add cmd_options argument Vladimir Sementsov-Ogievskiy
2020-10-26 17:18 ` [PATCH v3 25/25] simplebench: add bench-backup.py Vladimir Sementsov-Ogievskiy
2021-01-12 14:50 ` Max Reitz
2021-01-12 17:12 ` Vladimir Sementsov-Ogievskiy
2021-01-09 10:18 ` [PATCH v3 00/25] backup performance: block_status + async 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=9708f8d8-3afc-f30d-9245-20071763c5a3@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.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).