From: Feng Jiang <jiangfeng@kylinos.cn>
To: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, akpm@linux-foundation.org, kees@kernel.org,
andy@kernel.org, jiangfeng@kylinos.cn, ebiggers@kernel.org,
martin.petersen@oracle.com, mingo@kernel.org,
charlie@rivosinc.com, conor.dooley@microchip.com,
samuel.holland@sifive.com, linus.walleij@linaro.org,
nathan@kernel.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: [PATCH v4 5/8] lib/string_kunit: extend benchmarks to strnlen() and chr searches
Date: Fri, 23 Jan 2026 16:58:38 +0800 [thread overview]
Message-ID: <20260123085841.212468-6-jiangfeng@kylinos.cn> (raw)
In-Reply-To: <20260123085841.212468-1-jiangfeng@kylinos.cn>
Extend the string benchmarking suite to include strnlen(), strchr(),
and strrchr().
For character search functions strchr() and strrchr(), the benchmark
targets the NUL character. This ensures the entire string is scanned,
providing a consistent measure of full-length processing efficiency
comparable to strlen().
Suggested-by: Andy Shevchenko <andy@kernel.org>
Suggested-by: Eric Biggers <ebiggers@kernel.org>
Signed-off-by: Feng Jiang <jiangfeng@kylinos.cn>
Acked-by: Andy Shevchenko <andy@kernel.org>
---
lib/tests/string_kunit.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/lib/tests/string_kunit.c b/lib/tests/string_kunit.c
index 52798f426aa9..3d540ad78cda 100644
--- a/lib/tests/string_kunit.c
+++ b/lib/tests/string_kunit.c
@@ -857,6 +857,21 @@ static void string_bench_strlen(struct kunit *test)
STRING_BENCH_BUF(test, buf, len, strlen, buf);
}
+static void string_bench_strnlen(struct kunit *test)
+{
+ STRING_BENCH_BUF(test, buf, len, strnlen, buf, len);
+}
+
+static void string_bench_strchr(struct kunit *test)
+{
+ STRING_BENCH_BUF(test, buf, len, strchr, buf, '\0');
+}
+
+static void string_bench_strrchr(struct kunit *test)
+{
+ STRING_BENCH_BUF(test, buf, len, strrchr, buf, '\0');
+}
+
static struct kunit_case string_test_cases[] = {
KUNIT_CASE(string_test_memset16),
KUNIT_CASE(string_test_memset32),
@@ -883,6 +898,9 @@ static struct kunit_case string_test_cases[] = {
KUNIT_CASE(string_test_memtostr),
KUNIT_CASE(string_test_strends),
KUNIT_CASE(string_bench_strlen),
+ KUNIT_CASE(string_bench_strnlen),
+ KUNIT_CASE(string_bench_strchr),
+ KUNIT_CASE(string_bench_strrchr),
{}
};
--
2.25.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-01-23 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 8:58 [PATCH v4 0/8] riscv: optimize string functions and add kunit tests Feng Jiang
2026-01-23 8:58 ` [PATCH v4 1/8] lib/string_kunit: add correctness test for strlen() Feng Jiang
2026-01-23 8:58 ` [PATCH v4 2/8] lib/string_kunit: add correctness test for strnlen() Feng Jiang
2026-01-23 8:58 ` [PATCH v4 3/8] lib/string_kunit: add correctness test for strrchr() Feng Jiang
2026-01-23 8:58 ` [PATCH v4 4/8] lib/string_kunit: add performance benchmark for strlen() Feng Jiang
2026-01-23 11:02 ` Andy Shevchenko
2026-01-26 6:14 ` Feng Jiang
2026-01-26 9:28 ` Andy Shevchenko
2026-01-23 8:58 ` Feng Jiang [this message]
2026-01-23 8:58 ` [PATCH v4 6/8] riscv: lib: add strnlen() implementation Feng Jiang
2026-01-23 8:58 ` [PATCH v4 7/8] riscv: lib: add strchr() implementation Feng Jiang
2026-01-23 8:58 ` [PATCH v4 8/8] riscv: lib: add strrchr() implementation Feng Jiang
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=20260123085841.212468-6-jiangfeng@kylinos.cn \
--to=jiangfeng@kylinos.cn \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=andy@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=ebiggers@kernel.org \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=samuel.holland@sifive.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