public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Omar Sandoval <osandov@osandov.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: sbitmap: check cleared bits when iterating busy bits
Date: Mon, 3 Dec 2018 15:20:10 -0700	[thread overview]
Message-ID: <028ac9e9-18c7-c38e-8649-2663b2fe7160@kernel.dk> (raw)
In-Reply-To: <20181203220517.GD11220@vader>

On 12/3/18 3:05 PM, Omar Sandoval wrote:
> On Mon, Dec 03, 2018 at 02:56:17PM -0700, Jens Axboe wrote:
>> When we are iterating the set bits in a word, we also need to factor in
>> the cleared bits. Don't call fn() unless the bit is also not set in
>> the cleared word.
>>
>> Fixes: ea86ea2cdced ("sbitmap: ammortize cost of clearing bits")
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>>
>> diff --git a/include/linux/sbitmap.h b/include/linux/sbitmap.h
>> index 92806a2dbab7..9f374fbcdba6 100644
>> --- a/include/linux/sbitmap.h
>> +++ b/include/linux/sbitmap.h
>> @@ -283,6 +283,11 @@ static inline void __sbitmap_for_each_set(struct sbitmap *sb,
>>  			nr = find_next_bit(&word->word, depth, nr);
>>  			if (nr >= depth)
>>  				break;
>> +			/* if set in cleared, it's actually free */
>> +			if (test_bit(nr, &word->cleared)) {
>> +				nr++;
>> +				continue;
>> +			}
>>  			if (!fn(sb, (index << sb->shift) + nr, data))
>>  				return;
>>  
>> -- 
>> Jens Axboe
>>
> 
> How about something like this:
> 
> diff --git a/include/linux/sbitmap.h b/include/linux/sbitmap.h
> index f0f49bbb2617..fe9122386255 100644
> --- a/include/linux/sbitmap.h
> +++ b/include/linux/sbitmap.h
> @@ -265,12 +265,14 @@ static inline void __sbitmap_for_each_set(struct sbitmap *sb,
>  	nr = SB_NR_TO_BIT(sb, start);
>  
>  	while (scanned < sb->depth) {
> -		struct sbitmap_word *word = &sb->map[index];
> -		unsigned int depth = min_t(unsigned int, word->depth - nr,
> +		unsigned long word;
> +		unsigned int depth = min_t(unsigned int,
> +					   sb->map[index].depth - nr,
>  					   sb->depth - scanned);
>  
>  		scanned += depth;
> -		if (!word->word)
> +		word = sb->map[index].word & ~sb->map[index].cleared;
> +		if (!word)
>  			goto next;
>  
>  		/*
> @@ -280,7 +282,7 @@ static inline void __sbitmap_for_each_set(struct sbitmap *sb,
>  		 */
>  		depth += nr;
>  		while (1) {
> -			nr = find_next_bit(&word->word, depth, nr);
> +			nr = find_next_bit(&word, depth, nr);
>  			if (nr >= depth)
>  				break;
>  			if (!fn(sb, (index << sb->shift) + nr, data))
> 
> Might be marginally faster.

Yeah that looks fine as well, tests out good too.

-- 
Jens Axboe


      reply	other threads:[~2018-12-03 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 21:56 sbitmap: check cleared bits when iterating busy bits Jens Axboe
2018-12-03 22:05 ` Omar Sandoval
2018-12-03 22:20   ` Jens Axboe [this message]

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=028ac9e9-18c7-c38e-8649-2663b2fe7160@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@osandov.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