Re: [PATCH] hpsa: use find_first_zero_bit

[scameron]

On Sat, Jan 21, 2012 at 12:15:27AM +0900, Akinobu Mita wrote:
> Use find_first_zero_bit to find the first cleared bit in a memory region.
> 
> This also includes the following minor changes.
> - Use bitmap_zero
> - Reduce unnecessary atomic bitops usage

Ack.

This isn't performance sensitive code though, hpsa_find_target_lun()
only gets called during device discovery when a multi-lun device
like a tape drive with an auto changer is encountered.

I tried it out and it doesn't conflict with any of the patches
I sent up yesterday, and it works with a tape drive/autochanger.

-- steve
 
> 
> Signed-off-by: Akinobu Mita <akinobu.mita@xxxxxxxxx>
> Cc: "Stephen M. Cameron" <scameron@xxxxxxxxxxxxxxxxxx>
> Cc: iss_storagedev@xxxxxx
> Cc: "James E.J. Bottomley" <JBottomley@xxxxxxxxxxxxx>
> Cc: linux-scsi@xxxxxxxxxxxxxxx
> ---
>  drivers/scsi/hpsa.c |   18 ++++++++----------
>  1 files changed, 8 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
> index 7d14443..7f79ed8 100644
> --- a/drivers/scsi/hpsa.c
> +++ b/drivers/scsi/hpsa.c
> @@ -577,21 +577,19 @@ static int hpsa_find_target_lun(struct ctlr_info *h,
>  	int i, found = 0;
>  	DECLARE_BITMAP(lun_taken, HPSA_MAX_DEVICES);
>  
> -	memset(&lun_taken[0], 0, HPSA_MAX_DEVICES >> 3);
> +	bitmap_zero(lun_taken, HPSA_MAX_DEVICES);
>  
>  	for (i = 0; i < h->ndevices; i++) {
>  		if (h->dev[i]->bus == bus && h->dev[i]->target != -1)
> -			set_bit(h->dev[i]->target, lun_taken);
> +			__set_bit(h->dev[i]->target, lun_taken);
>  	}
>  
> -	for (i = 0; i < HPSA_MAX_DEVICES; i++) {
> -		if (!test_bit(i, lun_taken)) {
> -			/* *bus = 1; */
> -			*target = i;
> -			*lun = 0;
> -			found = 1;
> -			break;
> -		}
> +	i = find_first_zero_bit(lun_taken, HPSA_MAX_DEVICES);
> +	if (i < HPSA_MAX_DEVICES) {
> +		/* *bus = 1; */
> +		*target = i;
> +		*lun = 0;
> +		found = 1;
>  	}
>  	return !found;
>  }
> -- 
> 1.7.4.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/