public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Jia He <hejianet@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] libxfs: Optimize the loop for xfs_bitmap_empty
Date: Tue, 10 Nov 2015 07:54:03 -0500	[thread overview]
Message-ID: <20151110125403.GC21670@bfoster.bfoster> (raw)
In-Reply-To: <1447079482-10650-1-git-send-email-hejianet@gmail.com>

On Mon, Nov 09, 2015 at 10:31:22PM +0800, Jia He wrote:
> If there is any non zero bit in a long bitmap, it can jump out of the for 
> loop and finish the function as soon as possible.
> 
> Signed-off-by: Jia He <hejianet@gmail.com>
> Cc: Dave Chinner <david@fromorbit.com> 
> Cc: Brian Foster <bfoster@redhat.com> 
> ---
>  fs/xfs/libxfs/xfs_bit.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/fs/xfs/libxfs/xfs_bit.c b/fs/xfs/libxfs/xfs_bit.c
> index 0e8885a..84614b0 100644
> --- a/fs/xfs/libxfs/xfs_bit.c
> +++ b/fs/xfs/libxfs/xfs_bit.c
> @@ -36,6 +36,8 @@ xfs_bitmap_empty(uint *map, uint size)
>  
>  	for (i = 0; i < size; i++) {
>  		ret |= map[i];
> +		if (ret != 0)
> +			return 0;
>  	}
>  

Seems Ok to me, but if we're going to do this, why not just kill ret
entirely? For example, check 'if (map[i] != 0) return 0;' in the loop
and unconditionally return 1 if we make it to the end.

Brian

>  	return (ret == 0);
> -- 
> 2.5.0
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-11-10 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 14:31 [PATCH] libxfs: Optimize the loop for xfs_bitmap_empty Jia He
2015-11-10 12:54 ` Brian Foster [this message]
2015-11-11  6:37   ` hejianet
2015-11-11  7:49   ` [PATCH v2] " Jia He
2015-11-11 12:48     ` Brian Foster
2015-12-16  3:04       ` hejianet

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=20151110125403.GC21670@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=hejianet@gmail.com \
    --cc=xfs@oss.sgi.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