From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Martin Wilck <martin.wilck@suse.com>
Subject: Re: [PATCH V2] lib/sbitmap: kill 'depth' from sbitmap_word
Date: Tue, 08 Feb 2022 06:54:59 -0700 [thread overview]
Message-ID: <164432849902.112367.4722641037594849052.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220110072945.347535-1-ming.lei@redhat.com>
On Mon, 10 Jan 2022 15:29:45 +0800, Ming Lei wrote:
> Only the last sbitmap_word can have different depth, and all the others
> must have same depth of 1U << sb->shift, so not necessary to store it in
> sbitmap_word, and it can be retrieved easily and efficiently by adding
> one internal helper of __map_depth(sb, index).
>
> Remove 'depth' field from sbitmap_word, then the annotation of
> ____cacheline_aligned_in_smp for 'word' isn't needed any more.
>
> [...]
Applied, thanks!
[1/1] lib/sbitmap: kill 'depth' from sbitmap_word
commit: 3301bc53358a0eb0a0db65fd7a513cd4cb50c83a
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-02-08 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 7:29 [PATCH V2] lib/sbitmap: kill 'depth' from sbitmap_word Ming Lei
2022-02-08 3:23 ` Ming Lei
2022-02-08 7:46 ` Martin Wilck
2022-02-08 9:02 ` John Garry
2022-02-08 13:54 ` 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=164432849902.112367.4722641037594849052.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=martin.wilck@suse.com \
--cc=ming.lei@redhat.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