All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] libgfs2: Improve rgblocks2bitblocks()
Date: Fri, 18 Nov 2011 21:28:10 +0000	[thread overview]
Message-ID: <4EC6CDEA.4060603@redhat.com> (raw)
In-Reply-To: <15229912-62e2-480b-ab7e-672d89e3aa2f@zmail16.collab.prod.int.phx2.redhat.com>

On 18/11/11 20:52, Bob Peterson wrote:
> ----- Original Message -----
> | This patch reworks the rgblocks2bitblocks function which was
> | inefficient, difficult to read and generally unwieldy.
> |
> | As this is core code from the days of yore and fsck.gfs2 depends on
> | it,
> | I made sure to test the new function extensively, comparing its
> | outputs
> | with the original function over a large range of values for rgblocks
> | (up
> | to 195312500) and valid block sizes between 512 and 4096.
> |
> | All call points have been updated and, as a nice side effect, the run
> | time of the function is greatly reduced.
> |
> | Signed-off-by: Andrew Price<anprice@redhat.com>
> | +	while (blks_rgrp + blks_meta * bitblocks<  ((rgblocks - bitblocks)
>
> Hi,
>
> The patch looks good. There's only thing I'd do differently:
> I know the implied arithmetic operator order is correct, but
> I still prefer to see parens around statements like the above
> just for clarity. e.g.
>
> +	while (blks_rgrp + (blks_meta * bitblocks)<  ((rgblocks - bitblocks)
>
> I guess that's more of a style thing.

Yeah, it is more readable that way, I'll change it.

Andy



  reply	other threads:[~2011-11-18 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 20:30 [Cluster-devel] [PATCH] libgfs2: Improve rgblocks2bitblocks() Andrew Price
2011-11-18 20:52 ` Bob Peterson
2011-11-18 21:28   ` Andrew Price [this message]
2011-11-21 10:11 ` Steven Whitehouse

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=4EC6CDEA.4060603@redhat.com \
    --to=anprice@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.