qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	vsementsov@parallels.com, stefanha@redhat.com,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 06/14] blockjob: Add .commit and .abort block job actions
Date: Mon, 21 Sep 2015 18:29:17 -0400	[thread overview]
Message-ID: <560084BD.6010407@redhat.com> (raw)
In-Reply-To: <1442297513-7001-7-git-send-email-famz@redhat.com>



On 09/15/2015 02:11 AM, Fam Zheng wrote:
> Reviewed-by: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>  include/block/blockjob.h | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/include/block/blockjob.h b/include/block/blockjob.h
> index 3e7ad21..a7b497c 100644
> --- a/include/block/blockjob.h
> +++ b/include/block/blockjob.h
> @@ -50,6 +50,24 @@ typedef struct BlockJobDriver {
>       * manually.
>       */
>      void (*complete)(BlockJob *job, Error **errp);
> +
> +    /**
> +     * If the callback is not NULL, it will be invoked when all the jobs
> +     * belonging to the same transaction complete; or upon this job's
> +     * completion if it is not in a transaction. Skipped if NULL.
> +     *
> +     * Exactly one of .commit() and .abort() will be called for each job.
> +     */
> +    void (*commit)(BlockJob *job);
> +

I find this phrasing strange, but maybe it's just me. "Exactly one of
commit and abort will be called for each job" implies [to me] that it'd
be possible to call commit for one, but abort for different jobs [in a
transaction] -- but clearly we don't mean that. It is the "for each job"
that implies an iteration over a collection to me.

Just above we say "[commit] will be invoked when all the jobs belonging
to the same transaction are complete" which itself implies either all
jobs will be committed or all jobs will be aborted.

Maybe:

"All jobs will complete with a call to either .commit() or .abort() but
never both."

But I might be being too bikesheddy.

> +    /**
> +     * If the callback is not NULL, it will be invoked when any job in the
> +     * same transaction fails; or upon this job's failure (due to error or
> +     * cancellation) if it is not in a transaction. Skipped if NULL.
> +     *
> +     * Exactly one of .commit() and .abort() will be called for each job.
> +     */
> +    void (*abort)(BlockJob *job);
>  } BlockJobDriver;
>  
>  /**
> 

I'm probably just too picky.

Reviewed-by: John Snow <jsnow@redhat.com>

  reply	other threads:[~2015-09-21 22:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  6:11 [Qemu-devel] [PATCH v6 00/14] block: incremental backup transactions using BlockJobTxn Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 01/14] qapi: Add transaction support to block-dirty-bitmap operations Fam Zheng
2015-09-15 14:36   ` Eric Blake
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 02/14] iotests: add transactional incremental backup test Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 03/14] block: rename BlkTransactionState and BdrvActionOps Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 04/14] backup: Extract dirty bitmap handling as a separate function Fam Zheng
2015-09-18 11:02   ` Max Reitz
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 05/14] blockjob: Introduce reference count Fam Zheng
2015-09-21 22:19   ` John Snow
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 06/14] blockjob: Add .commit and .abort block job actions Fam Zheng
2015-09-21 22:29   ` John Snow [this message]
2015-09-22  2:15     ` Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 07/14] blockjob: Add "completed" and "ret" in BlockJob Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 08/14] blockjob: Simplify block_job_finish_sync Fam Zheng
2015-09-21 22:50   ` John Snow
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 09/14] block: Add block job transactions Fam Zheng
2015-09-18 11:16   ` Max Reitz
2015-09-21 23:23   ` John Snow
2015-09-22  2:32     ` Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 10/14] blockdev: make BlockJobTxn available to qmp 'transaction' Fam Zheng
2015-09-18 11:20   ` Max Reitz
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 11/14] block/backup: support block job transactions Fam Zheng
2015-09-15 14:43   ` Eric Blake
2015-09-18 11:40   ` Max Reitz
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 12/14] iotests: 124 - transactional failure test Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 13/14] qmp-commands.hx: Update the supported 'transaction' operations Fam Zheng
2015-09-15  6:11 ` [Qemu-devel] [PATCH v6 14/14] tests: add BlockJobTxn unit test Fam Zheng
2015-09-18 11:45   ` Max Reitz
2015-09-22  2:11     ` Fam Zheng

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=560084BD.6010407@redhat.com \
    --to=jsnow@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@parallels.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).