From: John Snow <jsnow@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: vsementsov@virtuozzo.com, famz@redhat.com, armbru@redhat.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v10 00/14] block: incremental backup transactions using BlockJobTxn
Date: Tue, 3 Nov 2015 17:07:25 -0500 [thread overview]
Message-ID: <5639301D.9020806@redhat.com> (raw)
In-Reply-To: <5638F2E8.2010703@redhat.com>
On 11/03/2015 12:46 PM, John Snow wrote:
>
>
> On 11/03/2015 10:22 AM, Stefan Hajnoczi wrote:
>> On Fri, Oct 23, 2015 at 07:56:38PM -0400, John Snow wrote:
>>> Welcome to V10!
>>>
>>> Where'd 8 and 9 go? Private off-list missives from Fam.
>>> Now you, I, and everyone on qemu-devel are staring at V10.
>>>
>>> What's new in V10?
>>>
>>> I replaced the per-action "transactional-cancel" parameter with
>>> a per-transaction paremeter named "err-cancel" which is implemented
>>> as an enum in case we want to add new behaviors in the future, such
>>> as a "jobs only" cancel mode.
>>>
>>> For now, it's "all" or "none", and if you use it with actions that
>>> do not support the latent transactional cancel, you will receive
>>> an error for your troubles.
>>
>> I left comments on a few patches.
>>
>> The "err-cancel" and "ActionCancelMode" naming does not describe the
>> concept fully, since successful block jobs will also behave differently
>> (waiting for each other to finish before fully completing).
>> "blockjob-transactions" is the best name I can think of that describes
>> the full concept rather than focus on just cancellation.
>>
>
> There's two hard problems in Computer Science...
>
> I mean, cancellation certainly is the biggest change in net behavior,
> though we are fiddling with the timings of the completion notices.
>
> OK, so continuing on my inability to name this feature ...
>
> blockjob-transactions = { individual, grouped, jobs-only }
>
> where we'd support "individual" as the default,
> "grouped" is the forced cancellation mode, and
> jobs-only is a hypothetical future mode that adds jobs to the group, and
> ignoring non-jobs' inability to join the transaction.
>
> Still, it seems weird to have:
> transaction 'properties': {'blockjob-transactions': 'grouped'},
> it feels redundant to me.
>
>
> How about:
>
> completion-mode = { individual, grouped }
>
> Avoids repeating "Transaction" and does not hyperfocus on cancellation.
>
Version "10.5" is on https://github.com/jnsnow/qemu.git
- Rebased on master to play nice with the new QAPI checkins (#3, #12)
- Fixed error path leak (#3)
- Renamed the Transaction Property and enum values (#12, #13) as above
("completion-mode", "individual", "grouped")
- Fixed a leak in the block_job_txn qtest (#14)
If the names and QMP interface look good I'll publish as v11.
--js
>> Besides that I'm happy with the QMP interface.
>>
prev parent reply other threads:[~2015-11-03 22:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 23:56 [Qemu-devel] [PATCH v10 00/14] block: incremental backup transactions using BlockJobTxn John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 01/14] qapi: Add transaction support to block-dirty-bitmap operations John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 02/14] iotests: add transactional incremental backup test John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 03/14] block: rename BlkTransactionState and BdrvActionOps John Snow
2015-11-03 16:33 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2015-11-03 17:32 ` John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 04/14] backup: Extract dirty bitmap handling as a separate function John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 05/14] blockjob: Introduce reference count and fix reference to job->bs John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 06/14] blockjob: Add .commit and .abort block job actions John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 07/14] blockjob: Add "completed" and "ret" in BlockJob John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 08/14] blockjob: Simplify block_job_finish_sync John Snow
2015-11-03 13:52 ` Stefan Hajnoczi
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 09/14] block: Add block job transactions John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 10/14] block/backup: Rely on commit/abort for cleanup John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 11/14] block: Add BlockJobTxn support to backup_run John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 12/14] block: add transactional properties John Snow
2015-11-03 15:17 ` Stefan Hajnoczi
2015-11-03 17:27 ` John Snow
2015-11-05 10:47 ` Stefan Hajnoczi
2015-11-05 18:52 ` John Snow
2015-11-05 19:35 ` Markus Armbruster
2015-11-05 19:43 ` John Snow
2015-11-06 8:32 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2015-11-06 16:36 ` Stefan Hajnoczi
2015-11-06 18:46 ` John Snow
2015-11-06 20:35 ` John Snow
2015-11-03 15:23 ` [Qemu-devel] " Eric Blake
2015-11-03 17:31 ` John Snow
2015-11-03 17:35 ` Eric Blake
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 13/14] iotests: 124 - transactional failure test John Snow
2015-10-23 23:56 ` [Qemu-devel] [PATCH v10 14/14] tests: add BlockJobTxn unit test John Snow
2015-11-02 21:06 ` [Qemu-devel] [PATCH v10 00/14] block: incremental backup transactions using BlockJobTxn John Snow
2015-11-03 15:22 ` Stefan Hajnoczi
2015-11-03 17:46 ` John Snow
2015-11-03 22:07 ` John Snow [this message]
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=5639301D.9020806@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).