public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>, Lin Feng <linf@wangsu.com>
Cc: paolo.valente@linaro.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: Re: [PATCH] Revert "bfq: Fix computation of shallow depth"
Date: Tue, 2 Feb 2021 07:20:16 -0700	[thread overview]
Message-ID: <f92a55b4-0743-a700-8296-e739f4fcf093@kernel.dk> (raw)
In-Reply-To: <20210202122836.GC17147@quack2.suse.cz>

On 2/2/21 5:28 AM, Jan Kara wrote:
> Hello!
> 
> On Fri 29-01-21 19:18:08, Lin Feng wrote:
>> This reverts commit 6d4d273588378c65915acaf7b2ee74e9dd9c130a.
>>
>> bfq.limit_depth passes word_depths[] as shallow_depth down to sbitmap core
>> sbitmap_get_shallow, which uses just the number to limit the scan depth of
>> each bitmap word, formula:
>> scan_percentage_for_each_word = shallow_depth / (1 << sbimap->shift) * 100%
> 
> Looking at sbitmap_get_shallow() again more carefully, I agree that I
> misunderstood how shallow_depth argument gets used and the original code
> was correct and I broke it. Thanks for spotting this!
> 
> What I didn't notice is that shallow_depth indeed gets used for each bitmap
> word separately and not for bitmap as a whole. I'd say this could use some
> more documentation but that's unrelated to your revert. So feel free to add:
> 
> Reviewed-by: Jan Kara <jack@suse.cz>

I don't have the original patch (neither directly nor in the archive), so
I had to hand-apply it. In any case, applied for 5.11, thanks.

-- 
Jens Axboe


  reply	other threads:[~2021-02-02 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210129111808.45796-1-linf@wangsu.com>
2021-02-01  7:32 ` [PATCH] Revert "bfq: Fix computation of shallow depth" Lin Feng
2021-02-01 19:03   ` Paolo Valente
2021-02-01 19:02 ` Paolo Valente
2021-02-02 12:28 ` Jan Kara
2021-02-02 14:20   ` Jens Axboe [this message]
2021-02-03  2:36     ` Lin Feng
2021-02-03  2:39       ` Jens Axboe

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=f92a55b4-0743-a700-8296-e739f4fcf093@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=linf@wangsu.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.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