qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-block@nongnu.org, Manos Pitsidianakis <el13635@mail.ntua.gr>
Subject: Re: [Qemu-devel] [PATCH v2 3/7] throttle: Make throttle_is_valid() a bit less verbose
Date: Tue, 29 Aug 2017 16:26:50 -0500	[thread overview]
Message-ID: <883c5683-97e6-d08f-4c90-803e53454047@redhat.com> (raw)
In-Reply-To: <763ffc40a26b17d54cf93f5a999e4656049fcf0c.1503580370.git.berto@igalia.com>

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

On 08/24/2017 08:24 AM, Alberto Garcia wrote:
> Use a pointer to the bucket instead of repeating cfg->buckets[i] all
> the time. This makes the code more concise and will help us expand the
> checks later and save a few line breaks.
> 
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
>  util/throttle.c | 15 +++++++--------
>  1 file changed, 7 insertions(+), 8 deletions(-)
> 
> diff --git a/util/throttle.c b/util/throttle.c
> index 9a6bda813c..bde56fe3de 100644
> --- a/util/throttle.c
> +++ b/util/throttle.c
> @@ -324,32 +324,31 @@ bool throttle_is_valid(ThrottleConfig *cfg, Error **errp)
>      }
>  
>      for (i = 0; i < BUCKETS_COUNT; i++) {
> -        if (cfg->buckets[i].avg < 0 ||
> -            cfg->buckets[i].max < 0 ||
> -            cfg->buckets[i].avg > THROTTLE_VALUE_MAX ||
> -            cfg->buckets[i].max > THROTTLE_VALUE_MAX) {
> +        LeakyBucket *bkt = &cfg->buckets[i];
> +        if (bkt->avg < 0 || bkt->max < 0 ||

Up to the maintainer, but I'd include a blank line between declarations
and code.

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

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


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

  reply	other threads:[~2017-08-29 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 13:24 [Qemu-devel] [PATCH v2 0/7] Misc throttle fixes Alberto Garcia
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 1/7] throttle: Fix wrong variable name in the header documentation Alberto Garcia
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 2/7] throttle: Update the throttle_fix_bucket() documentation Alberto Garcia
2017-08-29 21:25   ` Eric Blake
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 3/7] throttle: Make throttle_is_valid() a bit less verbose Alberto Garcia
2017-08-29 21:26   ` Eric Blake [this message]
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 4/7] throttle: Remove throttle_fix_bucket() / throttle_unfix_bucket() Alberto Garcia
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 5/7] throttle: Make LeakyBucket.avg and LeakyBucket.max integer types Alberto Garcia
2017-08-29 21:29   ` Eric Blake
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 6/7] throttle: Make burst_length 64bit and add range checks Alberto Garcia
2017-08-29 21:30   ` Eric Blake
2017-08-24 13:24 ` [Qemu-devel] [PATCH v2 7/7] throttle: Test the valid range of config values Alberto Garcia
2017-08-29 16:43 ` [Qemu-devel] [PATCH v2 0/7] Misc throttle fixes 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=883c5683-97e6-d08f-4c90-803e53454047@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berto@igalia.com \
    --cc=el13635@mail.ntua.gr \
    --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 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).