All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Nefedov <anton.nefedov@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
	den@virtuozzo.com, berto@igalia.com
Subject: Re: [Qemu-devel] [PATCH v9 1/9] mirror: inherit supported write/zero flags
Date: Tue, 15 May 2018 17:59:30 +0300	[thread overview]
Message-ID: <7bb6f859-6b8c-7d70-d691-703c040ca9be@virtuozzo.com> (raw)
In-Reply-To: <d61d47db-a121-a3e3-5bd8-312af5511991@redhat.com>



On 15/5/2018 5:35 PM, Eric Blake wrote:
> On 05/08/2018 09:58 AM, Anton Nefedov wrote:
>> diff --git a/block/mirror.c b/block/mirror.c
>> index 820f512..a22ddef 100644
>> --- a/block/mirror.c
>> +++ b/block/mirror.c
>> @@ -1098,6 +1098,15 @@ static BlockDriver bdrv_mirror_top = {
>>       .bdrv_child_perm            = bdrv_mirror_top_child_perm,
>>   };
>> +static void mirror_top_set_supported_flags(BlockDriverState *bs)
>> +{
>> +    bs->supported_write_flags = BDRV_REQ_FUA &
>> +        bs->backing->bs->supported_write_flags;
>> +    bs->supported_zero_flags =
>> +        (BDRV_REQ_FUA | BDRV_REQ_MAY_UNMAP) &
>> +        bs->backing->bs->supported_zero_flags;
>> +}
>> +
> 
> This is a pretty short static function...
> 
>>   static void mirror_start_job(const char *job_id, BlockDriverState *bs,
>>                                int creation_flags, BlockDriverState 
>> *target,
>>                                const char *replaces, int64_t speed,
>> @@ -1163,6 +1172,8 @@ static void mirror_start_job(const char *job_id, 
>> BlockDriverState *bs,
>>           return;
>>       }
>> +    mirror_top_set_supported_flags(mirror_top_bs);
> 
> ...with exactly one caller.  Wouldn't it be easier to just inline it?
> 

idk, I felt mirror_start_job() was quite massive already, even
considering there are just a few new lines.

  reply	other threads:[~2018-05-15 14:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 14:58 [Qemu-devel] [PATCH v9 0/9] qcow2: cluster space preallocation Anton Nefedov
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 1/9] mirror: inherit supported write/zero flags Anton Nefedov
2018-05-15 14:35   ` Eric Blake
2018-05-15 14:59     ` Anton Nefedov [this message]
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 2/9] blkverify: set " Anton Nefedov
2018-05-15 14:37   ` Eric Blake
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 3/9] quorum: " Anton Nefedov
2018-05-15 14:38   ` Eric Blake
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 4/9] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2018-05-14 10:29   ` Alberto Garcia
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 5/9] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 6/9] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2018-05-14 11:50   ` Alberto Garcia
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 7/9] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 8/9] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2018-05-14 13:09   ` Alberto Garcia
2018-05-08 14:58 ` [Qemu-devel] [PATCH v9 9/9] iotest 134: test cluster-misaligned encrypted write Anton Nefedov

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=7bb6f859-6b8c-7d70-d691-703c040ca9be@virtuozzo.com \
    --to=anton.nefedov@virtuozzo.com \
    --cc=berto@igalia.com \
    --cc=den@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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.