All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/6] block-commit: Expose granularity
Date: Thu, 10 Apr 2014 16:40:11 +0200	[thread overview]
Message-ID: <5346AD4B.2050004@redhat.com> (raw)
In-Reply-To: <534421EB.9050801@redhat.com>

On 08.04.2014 18:20, Eric Blake wrote:
> On 04/08/2014 06:50 AM, Max Reitz wrote:
>> Allow QMP users to manipulate the granularity used in the block-commit
>> command.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>
>> +++ b/include/block/block_int.h
>> @@ -426,6 +426,7 @@ void stream_start(BlockDriverState *bs, BlockDriverState *base,
>>    * @top: Top block device to be committed.
>>    * @base: Block device that will be written into, and become the new top.
>>    * @speed: The maximum speed, in bytes per second, or 0 for unlimited.
>> + * @granularity: The granularity, in bytes, or 0 for a default value.
>>    * @on_error: The action to take upon error.
>>    * @cb: Completion function for the job.
>>    * @opaque: Opaque pointer value passed to @cb.
>> @@ -433,7 +434,7 @@ void stream_start(BlockDriverState *bs, BlockDriverState *base,
>>    *
>>    */
>>   void commit_start(BlockDriverState *bs, BlockDriverState *base,
>> -                 BlockDriverState *top, int64_t speed,
>> +                 BlockDriverState *top, int64_t speed, int64_t granularity,
>>                    BlockdevOnError on_error, BlockDriverCompletionFunc *cb,
>>                    void *opaque, Error **errp);
> Worth fixing the indentation while you are touching this?

I'm always in favor of code style clean-up. ;-)

Max

> Reviewed-by: Eric Blake <eblake@redhat.com>

  reply	other threads:[~2014-04-10 15:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 12:50 [Qemu-devel] [PATCH v2 0/6] qemu-img: Implement commit like QMP Max Reitz
2014-04-08 12:50 ` [Qemu-devel] [PATCH v2 1/6] block-commit: Expose granularity Max Reitz
2014-04-08 15:09   ` Kevin Wolf
2014-04-08 16:20   ` Eric Blake
2014-04-10 14:40     ` Max Reitz [this message]
2014-04-08 12:50 ` [Qemu-devel] [PATCH v2 2/6] block-commit: speed is an optional parameter Max Reitz
2014-04-08 15:07   ` Kevin Wolf
2014-04-10 14:41     ` Max Reitz
2014-04-08 16:24   ` Eric Blake
2014-04-08 12:50 ` [Qemu-devel] [PATCH v2 3/6] qemu-img: Implement commit like QMP Max Reitz
2014-04-08 15:14   ` Kevin Wolf
2014-04-08 16:39     ` Eric Blake
2014-04-10 14:32     ` Max Reitz
2014-04-11 12:54       ` Kevin Wolf
2014-04-08 12:50 ` [Qemu-devel] [PATCH v2 4/6] qemu-img: Enable progress output for commit Max Reitz
2014-04-08 15:34   ` Kevin Wolf
2014-04-08 16:53     ` Eric Blake
2014-04-09  8:27       ` Kevin Wolf
2014-04-10 14:37     ` Max Reitz
2014-04-08 12:50 ` [Qemu-devel] [PATCH v2 5/6] qemu-img: Specify backing file " Max Reitz
2014-04-08 17:01   ` Eric Blake
2014-04-10 14:42     ` Max Reitz
2014-04-10  9:05   ` Fam Zheng
2014-04-10 14:45     ` Max Reitz
2014-04-08 12:50 ` [Qemu-devel] [PATCH v2 6/6] iotests: Commit tests for two-layer backing chains Max Reitz
2014-04-08 17:10   ` Eric Blake

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=5346AD4B.2050004@redhat.com \
    --to=mreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.