From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Feng Jiang <jiangfeng@kylinos.cn>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, kees@kernel.org, andy@kernel.org,
akpm@linux-foundation.org, ebiggers@kernel.org,
martin.petersen@oracle.com, ardb@kernel.org,
ajones@ventanamicro.com, conor.dooley@microchip.com,
samuel.holland@sifive.com, linus.walleij@linaro.org,
nathan@kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2 08/14] lib/string_kunit: add performance benchmark for strlen()
Date: Tue, 13 Jan 2026 10:46:16 +0200 [thread overview]
Message-ID: <aWYGWLEekWh3jJVf@smile.fi.intel.com> (raw)
In-Reply-To: <20260113082748.250916-9-jiangfeng@kylinos.cn>
On Tue, Jan 13, 2026 at 04:27:42PM +0800, Feng Jiang wrote:
> Introduce a benchmark to compare the architecture-optimized strlen()
> implementation against the generic C version (__generic_strlen).
>
> The benchmark uses a table-driven approach to evaluate performance
> across different string lengths (short, medium, and long). It employs
> ktime_get() for timing and get_random_bytes() followed by null-byte
> filtering to generate test data that prevents early termination.
>
> This helps in quantifying the performance gains of architecture-specific
> optimizations on various platforms.
...
> +static void string_test_strlen_bench(struct kunit *test)
> +{
> + char *buf;
> + size_t buf_len, iters;
> + ktime_t start, end;
> + u64 time_arch, time_generic;
> +
> + buf_len = get_max_bench_len(bench_cases, ARRAY_SIZE(bench_cases)) + 1;
> +
> + buf = kunit_kzalloc(test, buf_len, GFP_KERNEL);
> + KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
> +
> + for (size_t i = 0; i < ARRAY_SIZE(bench_cases); i++) {
> + get_random_nonzero_bytes(buf, bench_cases[i].len);
> + buf[bench_cases[i].len] = '\0';
> +
> + iters = bench_cases[i].iterations;
> +
> + /* 1. Benchmark the architecture-optimized version */
> + start = ktime_get();
> + for (unsigned int j = 0; j < iters; j++) {
> + OPTIMIZER_HIDE_VAR(buf);
> + (void)strlen(buf);
First Q: Are you sure the compiler doesn't replace this with __builtin_strlen() ?
> + }
> + end = ktime_get();
> + time_arch = ktime_to_ns(ktime_sub(end, start));
> +
> + /* 2. Benchmark the generic C version */
> + start = ktime_get();
> + for (unsigned int j = 0; j < iters; j++) {
> + OPTIMIZER_HIDE_VAR(buf);
> + (void)__generic_strlen(buf);
> + }
Are you sure the warmed up caches do not affect the benchmark? I think you need
to flush / make caches dirty or so on each iteration.
> + end = ktime_get();
> + time_generic = ktime_to_ns(ktime_sub(end, start));
> +
> + string_bench_report(test, "strlen", &bench_cases[i],
> + time_arch, time_generic);
> + }
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-13 8:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 8:27 [PATCH v2 00/14] riscv: optimize string functions and add kunit tests Feng Jiang
2026-01-13 8:27 ` [PATCH v2 01/14] lib/string: extract generic strlen() into __generic_strlen() Feng Jiang
2026-01-13 8:33 ` Andy Shevchenko
2026-01-14 0:01 ` Eric Biggers
2026-01-14 1:41 ` Feng Jiang
2026-01-14 7:07 ` Andy Shevchenko
2026-01-14 10:10 ` David Laight
2026-01-15 6:50 ` Feng Jiang
2026-01-15 6:55 ` Andy Shevchenko
2026-01-13 8:27 ` [PATCH v2 02/14] lib/string: extract generic strnlen() into __generic_strnlen() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 03/14] lib/string: extract generic strchr() into __generic_strchr() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 04/14] lib/string: extract generic strrchr() into __generic_strrchr() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 05/14] lib/string_kunit: add correctness test for strlen Feng Jiang
2026-01-13 8:27 ` [PATCH v2 06/14] lib/string_kunit: add correctness test for strnlen Feng Jiang
2026-01-13 8:41 ` Andy Shevchenko
2026-01-13 8:27 ` [PATCH v2 07/14] lib/string_kunit: add correctness test for strrchr() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 08/14] lib/string_kunit: add performance benchmark for strlen() Feng Jiang
2026-01-13 8:46 ` Andy Shevchenko [this message]
2026-01-14 6:14 ` Feng Jiang
2026-01-14 7:04 ` Feng Jiang
2026-01-14 7:21 ` Andy Shevchenko
2026-01-14 8:05 ` Feng Jiang
2026-01-14 10:21 ` David Laight
2026-01-15 6:24 ` Feng Jiang
2026-01-15 10:40 ` David Laight
2026-01-18 11:11 ` kernel test robot
2026-01-13 8:27 ` [PATCH v2 09/14] lib/string_kunit: add performance benchmark for strnlen() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 10/14] lib/string_kunit: add performance benchmark for strchr() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 11/14] lib/string_kunit: add performance benchmark for strrchr() Feng Jiang
2026-01-13 8:27 ` [PATCH v2 12/14] riscv: lib: add strnlen implementation Feng Jiang
2026-01-13 8:48 ` Andy Shevchenko
2026-01-13 8:27 ` [PATCH v2 13/14] riscv: lib: add strchr implementation Feng Jiang
2026-01-13 8:27 ` [PATCH v2 14/14] riscv: lib: add strrchr implementation Feng Jiang
2026-01-13 8:52 ` [PATCH v2 00/14] riscv: optimize string functions and add kunit tests Andy Shevchenko
2026-01-15 4:43 ` Joel Stanley
2026-01-19 9:24 ` 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=aWYGWLEekWh3jJVf@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=andy@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=ebiggers@kernel.org \
--cc=jiangfeng@kylinos.cn \
--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=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