qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 05/12] job: @force parameter for job_cancel_sync()


From: Vladimir Sementsov-Ogievskiy
Subject: Re: [PATCH v4 05/12] job: @force parameter for job_cancel_sync()
Date: Wed, 15 Sep 2021 10:07:59 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0

14.09.2021 20:20, Hanna Reitz wrote:
On 08.09.21 18:33, Vladimir Sementsov-Ogievskiy wrote:
07.09.2021 15:42, Hanna Reitz wrote:
Callers should be able to specify whether they want job_cancel_sync() to
force-cancel the job or not.

In fact, almost all invocations do not care about consistency of the
result and just want the job to terminate as soon as possible, so they
should pass force=true.  The replication block driver is the exception,
specifically the active commit job it runs.

As for job_cancel_sync_all(), all callers want it to force-cancel all
jobs, because that is the point of it: To cancel all remaining jobs as
quickly as possible (generally on process termination).  So make it
invoke job_cancel_sync() with force=true.

This changes some iotest outputs, because quitting qemu while a mirror
job is active will now lead to it being cancelled instead of completed,
which is what we want.  (Cancelling a READY mirror job with force=false
may take an indefinite amount of time, which we do not want when
quitting.  If users want consistent results, they must have all jobs be
done before they quit qemu.)

Buglink:https://gitlab.com/qemu-project/qemu/-/issues/462
Signed-off-by: Hanna Reitz<hreitz@redhat.com>

Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>

Thanks!

Do you plan on taking this series or should I?


Hmm, right, I'm a maintainer!) I will, sorry for a delay.

--
Best regards,
Vladimir



reply via email to

[Prev in Thread] Current Thread [Next in Thread]