From: Yu Kuai <yukuai1@huaweicloud.com>
To: Jan Kara <jack@suse.cz>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: yukuai@kernel.org, axboe@kernel.dk, akpm@linux-foundation.org,
yang.yang@vivo.com, dlemoal@kernel.org, ming.lei@redhat.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com, Omar Sandoval <osandov@fb.com>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v2 1/2] lib/sbitmap: convert shallow_depth from one word to the whole sbitmap
Date: Fri, 1 Aug 2025 08:24:58 +0800 [thread overview]
Message-ID: <12d82243-237c-d890-a975-392b151d55a9@huaweicloud.com> (raw)
In-Reply-To: <imit4dkxy55c6a6tfqzaa6hf67nrawedotc3rzltlmmgmf3b3t@nde6h6cy3agw>
Hi,
在 2025/08/01 0:27, Jan Kara 写道:
> On Thu 31-07-25 10:38:58, Yu Kuai wrote:
>> Hi,
>>
>> 在 2025/07/31 2:24, Yu Kuai 写道:
>>> hi, Jan!
>>>
>>> 在 2025/7/30 21:03, Jan Kara 写道:
>>>> I think having two APIs will be even more confusing than the current
>>>> state.
>>>> But as I wrote I think you can have API to specify shallow depth in total
>>>> size and in sbitmap_queue_get_shallow() do:
>>>>
>>>> shallow_per_word = (shallow_depth << sb->shift) / sb->depth;
>> In order to consider the last word, I think we should use __map_depth()
>> here.
>
> Right.
>
>>>> rounding_index = shallow_depth - shallow_per_word * sb->depth;
>> And then it's not possible to calculate this rounding index easily. How
>> about following, although the reminder handling is not perfect.
>>
>> static unsigned int __map_depth_with_shallow(const struct sbitmap *sb,
>> int index,
>> unsigned int shallow_depth)
>> {
>> unsigned int word_depth = __map_depth(sb, index);
>> unsigned int shallow_word_depth = word_depth * shallow_depth;
>> unsigned reminder = do_div(shallow_word_depth, sb->depth);
>>
>> if (reminder && !(index & 0x1))
>
> Well, why not:
> if (remainder > index)
Do you mean reminder > index * shallow_depth? This looks correct, and
with the consideration for the last word:
if (index == sb->map_nr - 1)
shallow_word_depth = max(shallow_word_depth, 1);
else if (reminder > index * shallow_depth)
shallow_word_depth++;
Thanks,
Kuai
> ?
>
> That should accurately distribute the remainder across the remaining words,
> shouldn't it?
>
>> shallow_word_depth++;
>>
>> return shallow_word_depth;
>> }
>
> Honza
>
next prev parent reply other threads:[~2025-08-01 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 3:19 [PATCH v2 0/2] lib/sbitmap: convert shallow_depth from one word to the whole sbitmap Yu Kuai
2025-07-29 3:19 ` [PATCH v2 1/2] " Yu Kuai
2025-07-29 10:16 ` Jan Kara
2025-07-30 2:03 ` Yu Kuai
2025-07-30 13:03 ` Jan Kara
2025-07-30 18:24 ` Yu Kuai
2025-07-31 2:38 ` Yu Kuai
2025-07-31 16:27 ` Jan Kara
2025-08-01 0:24 ` Yu Kuai [this message]
2025-08-01 7:44 ` Yu Kuai
2025-07-29 3:19 ` [PATCH v2 2/2] lib/sbitmap: make sbitmap_get_shallow() static Yu Kuai
2025-07-29 9:36 ` Jan Kara
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=12d82243-237c-d890-a975-392b151d55a9@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=jack@suse.cz \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=yang.yang@vivo.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
--cc=yukuai@kernel.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;
as well as URLs for NNTP newsgroup(s).