From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 5/5] block/block-copy: use aio-task-pool API
Date: Wed, 29 Apr 2020 13:55:43 +0200 [thread overview]
Message-ID: <1abe2617-4cc6-85c5-8c81-e2fa1fe4b5dc@redhat.com> (raw)
In-Reply-To: <20200429061039.12687-6-vsementsov@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 2448 bytes --]
On 29.04.20 08:10, Vladimir Sementsov-Ogievskiy wrote:
> Run block_copy iterations in parallel in aio tasks.
>
> Changes:
> - BlockCopyTask becomes aio task structure. Add zeroes field to pass
> it to block_copy_do_copy
> - add call state - it's a state of one call of block_copy(), shared
> between parallel tasks. For now used only to keep information about
> first error: is it read or not.
> - convert block_copy_dirty_clusters to aio-task loop.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> block/block-copy.c | 104 +++++++++++++++++++++++++++++++++++++++------
> 1 file changed, 91 insertions(+), 13 deletions(-)
>
> diff --git a/block/block-copy.c b/block/block-copy.c
> index 5cf032c4d8..f5ef91f292 100644
> --- a/block/block-copy.c
> +++ b/block/block-copy.c
[...]
> @@ -261,6 +278,30 @@ void block_copy_set_progress_meter(BlockCopyState *s, ProgressMeter *pm)
> s->progress = pm;
> }
>
> +/* Takes ownership on @task */
Still *of
> +static coroutine_fn int block_copy_task_run(AioTaskPool *pool,
> + BlockCopyTask *task)
> +{
> + if (!pool) {
> + int ret = task->task.func(&task->task);
> +
> + g_free(task);
> + return ret;
> + }
> +
> + aio_task_pool_wait_slot(pool);
> + if (aio_task_pool_status(pool) < 0) {
> + co_put_to_shres(task->s->mem, task->bytes);
> + block_copy_task_end(task, -EAGAIN);
It looks like you may have missed my nit picks on v2 regarding this
patch, so I’m going to ask again whether -ECANCELED might be better here
(even though it still doesn’t really matter).
> + g_free(task);
> + return aio_task_pool_status(pool);
And whether it may be better to return a constant like -ECANCELED here,
because how a previous task failed shouldn’t really concern this task
(or its error code).
> + }
> +
> + aio_task_pool_start_task(pool, &task->task);
> +
> + return 0;
> +}
> +
> /*
> * block_copy_do_copy
> *
[...]
> @@ -525,25 +590,38 @@ static int coroutine_fn block_copy_dirty_clusters(BlockCopyState *s,
[...]
> +out:
> + if (aio) {
> + aio_task_pool_wait_all(aio);
> + if (ret == 0) {
> + ret = aio_task_pool_status(aio);
> + }
> + g_free(aio);
I’d still prefer aio_task_pool_free().
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-29 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 6:10 [PATCH v3 0/5] block-copy: use aio-task-pool Vladimir Sementsov-Ogievskiy
2020-04-29 6:10 ` [PATCH v3 1/5] block/block-copy: rename in-flight requests to tasks Vladimir Sementsov-Ogievskiy
2020-04-29 10:57 ` Max Reitz
2020-04-29 6:10 ` [PATCH v3 2/5] block/block-copy: alloc task on each iteration Vladimir Sementsov-Ogievskiy
2020-04-29 6:10 ` [PATCH v3 3/5] block/block-copy: add state pointer to BlockCopyTask Vladimir Sementsov-Ogievskiy
2020-04-29 6:10 ` [PATCH v3 4/5] block/block-copy: refactor task creation Vladimir Sementsov-Ogievskiy
2020-04-29 11:38 ` Max Reitz
2020-04-29 11:54 ` Vladimir Sementsov-Ogievskiy
2020-04-29 11:56 ` Max Reitz
2020-04-29 12:04 ` Vladimir Sementsov-Ogievskiy
2020-04-29 6:10 ` [PATCH v3 5/5] block/block-copy: use aio-task-pool API Vladimir Sementsov-Ogievskiy
2020-04-29 11:55 ` Max Reitz [this message]
2020-04-29 12:11 ` 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=1abe2617-4cc6-85c5-8c81-e2fa1fe4b5dc@redhat.com \
--to=mreitz@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).