From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Yury Norov <yury.norov@gmail.com>
Subject: [PATCH 3/3] bitmap: add tests for find_next_bit()
Date: Wed, 26 Oct 2022 21:38:10 -0700 [thread overview]
Message-ID: <20221027043810.350460-4-yury.norov@gmail.com> (raw)
In-Reply-To: <20221027043810.350460-1-yury.norov@gmail.com>
Test out-of-line and inline paths of find_next_bit().
Signed-off-by: Yury Norov <yury.norov@gmail.com>
---
lib/test_bitmap.c | 23 +++++++++++++++++++++--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/lib/test_bitmap.c b/lib/test_bitmap.c
index a8005ad3bd58..becf9c7a95a1 100644
--- a/lib/test_bitmap.c
+++ b/lib/test_bitmap.c
@@ -221,7 +221,7 @@ static void __init test_zero_clear(void)
expect_eq_pbl("", bmap, 1024);
}
-static void __init test_find_nth_bit(void)
+static void __init test_find_bit(void)
{
unsigned long b, bit, cnt = 0;
DECLARE_BITMAP(bmap, 64 * 3);
@@ -236,6 +236,25 @@ static void __init test_find_nth_bit(void)
__set_bit(80, bmap);
__set_bit(123, bmap);
+ expect_eq_uint(10, find_next_bit(bmap, 64 * 3, 0));
+ expect_eq_uint(20, find_next_bit(bmap, 64 * 3, 11));
+ expect_eq_uint(30, find_next_bit(bmap, 64 * 3, 21));
+ expect_eq_uint(40, find_next_bit(bmap, 64 * 3, 31));
+ expect_eq_uint(50, find_next_bit(bmap, 64 * 3, 41));
+ expect_eq_uint(60, find_next_bit(bmap, 64 * 3, 51));
+ expect_eq_uint(80, find_next_bit(bmap, 64 * 3, 61));
+ expect_eq_uint(123, find_next_bit(bmap, 64 * 3, 81));
+
+ /* Test small_const_nbits_off() optimization path */
+ expect_eq_uint(10, find_next_bit(bmap, 20 + 0, 0));
+ expect_eq_uint(20, find_next_bit(bmap, 20 + 11, 11));
+ expect_eq_uint(30, find_next_bit(bmap, 20 + 21, 21));
+ expect_eq_uint(40, find_next_bit(bmap, 20 + 31, 31));
+ expect_eq_uint(50, find_next_bit(bmap, 20 + 41, 41));
+ expect_eq_uint(60, find_next_bit(bmap, 20 + 51, 51));
+ expect_eq_uint(80, find_next_bit(bmap, 20 + 61, 61));
+ expect_eq_uint(90, find_next_bit(bmap, 20 + 70, 81));
+
expect_eq_uint(10, find_nth_bit(bmap, 64 * 3, 0));
expect_eq_uint(20, find_nth_bit(bmap, 64 * 3, 1));
expect_eq_uint(30, find_nth_bit(bmap, 64 * 3, 2));
@@ -1226,7 +1245,7 @@ static void __init selftest(void)
test_bitmap_print_buf();
test_bitmap_const_eval();
- test_find_nth_bit();
+ test_find_bit();
test_for_each_set_bit();
test_for_each_set_bit_from();
test_for_each_clear_bit();
--
2.34.1
next prev parent reply other threads:[~2022-10-27 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:38 [PATCH 0/3] bitmap: optimize small_const path for Yury Norov
2022-10-27 4:38 ` [PATCH 1/3] bitmap: switch from inline to __always_inline Yury Norov
2022-10-27 4:38 ` [PATCH 2/3] bitmap: improve small_const case for find_next() functions Yury Norov
2022-10-27 4:38 ` Yury Norov [this message]
2022-11-03 2:09 ` [PATCH 0/3] bitmap: optimize small_const path for Yury Norov
2022-12-08 3:32 ` Yury Norov
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=20221027043810.350460-4-yury.norov@gmail.com \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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).