From: Jens Axboe <axboe@kernel.dk>
To: John Garry <john.garry@huawei.com>
Cc: bvanassche@acm.org, osandov@fb.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, hare@suse.com
Subject: Re: [PATCH] sbitmap: Consider cleared bits in sbitmap_bitmap_show()
Date: Wed, 1 Jul 2020 10:53:28 -0600 [thread overview]
Message-ID: <122e0d4d-d9b2-a81e-b8ce-fa8636eabe1b@kernel.dk> (raw)
In-Reply-To: <1593590785-191512-1-git-send-email-john.garry@huawei.com>
On 7/1/20 2:06 AM, John Garry wrote:
> sbitmap works by maintaining separate bitmaps of set and cleared bits.
> The set bits are cleared in a batch, to save the burden of continuously
> locking the "word" map to unset.
>
> sbitmap_bitmap_show() only shows the set bits (in "word"), which is not
> too much use, so mask out the cleared bits.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-07-01 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 8:06 [PATCH] sbitmap: Consider cleared bits in sbitmap_bitmap_show() John Garry
2020-07-01 16:53 ` 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=122e0d4d-d9b2-a81e-b8ce-fa8636eabe1b@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.com \
--cc=john.garry@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.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;
as well as URLs for NNTP newsgroup(s).