qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 01/11] block: prepare write threshold code for thread safety
Date: Mon, 10 Jul 2017 18:16:12 +0200	[thread overview]
Message-ID: <906526d4-218b-6a19-09cd-9dbaa014261d@redhat.com> (raw)
In-Reply-To: <20170710132121.GF14195@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On 10/07/2017 15:21, Stefan Hajnoczi wrote:
> On Thu, Jul 06, 2017 at 06:38:18PM +0200, Paolo Bonzini wrote:
>> Code refactoring only.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  block/write-threshold.c | 28 ++++++++++++++++------------
>>  1 file changed, 16 insertions(+), 12 deletions(-)
>>
>> diff --git a/block/write-threshold.c b/block/write-threshold.c
>> index 0bd1a01c86..c8ebc32b4d 100644
>> --- a/block/write-threshold.c
>> +++ b/block/write-threshold.c
>> @@ -37,18 +37,22 @@ static void write_threshold_disable(BlockDriverState *bs)
>>      }
>>  }
>>  
>> +static uint64_t exceeded_amount(const BdrvTrackedRequest *req,
>> +                                uint64_t thres)
> 
> Not a reason to respin, but I would prefer a more specific name so the
> intent of the code is easier to understand: exceeded_threshold() instead
> of exceeded_amount().
> 
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

It's the amount by which the request exceeds threshold...  Not sure what
name would be best.

Paolo


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-07-10 16:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 16:38 [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part Paolo Bonzini
2017-07-06 16:38 ` [Qemu-devel] [PATCH 01/11] block: prepare write threshold code for thread safety Paolo Bonzini
2017-07-06 16:51   ` Eric Blake
2017-07-10 13:21   ` Stefan Hajnoczi
2017-07-10 16:16     ` Paolo Bonzini [this message]
2017-07-10 16:22       ` Eric Blake
2017-07-06 16:38 ` [Qemu-devel] [PATCH 02/11] block: make write-threshold thread-safe Paolo Bonzini
2017-07-06 16:52   ` Eric Blake
2017-07-10 15:42   ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 03/11] util: use RCU accessors for notifiers Paolo Bonzini
2017-07-10 15:52   ` Stefan Hajnoczi
2017-07-10 16:06     ` Paolo Bonzini
2017-07-11  9:45       ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 04/11] block: make before-write notifiers thread-safe Paolo Bonzini
2017-07-10 15:50   ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 05/11] block-backup: add reqs_lock Paolo Bonzini
2017-07-10 15:57   ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 06/11] block: add a few more notes on locking Paolo Bonzini
2017-07-10 15:57   ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 07/11] block: do not acquire AioContext in check_to_replace_node Paolo Bonzini
2017-07-10 15:58   ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 08/11] block: drain I/O around key management Paolo Bonzini
2017-07-10 16:01   ` Stefan Hajnoczi
2017-07-06 16:38 ` [Qemu-devel] [PATCH 09/11] block/replication: do not acquire AioContext Paolo Bonzini
2017-07-06 16:38 ` [Qemu-devel] [PATCH 10/11] block: do not take AioContext around reopen Paolo Bonzini
2017-07-06 16:38 ` [Qemu-devel] [PATCH 11/11] block/snapshot: do not take AioContext lock Paolo Bonzini
2017-07-10 16:24   ` Stefan Hajnoczi
2017-07-10 16:27     ` Paolo Bonzini
2017-07-11  9:43       ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-11  9:48         ` Paolo Bonzini
2017-07-12 10:42           ` Stefan Hajnoczi
2017-07-06 23:48 ` [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part no-reply
2017-07-07  0:06   ` Fam Zheng
2017-07-10 16:25 ` Stefan Hajnoczi

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=906526d4-218b-6a19-09cd-9dbaa014261d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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).