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, akpm@linux-foundation.org, kees@kernel.org,
andy@kernel.org, ebiggers@kernel.org, martin.petersen@oracle.com,
sohil.mehta@intel.com, charlie@rivosinc.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 v5 4/8] lib/string_kunit: add performance benchmark for strlen()
Date: Tue, 27 Jan 2026 11:50:50 +0200 [thread overview]
Message-ID: <aXiKelsJF-SiqnVS@smile.fi.intel.com> (raw)
In-Reply-To: <dcdb82e8-691a-4cc1-88d5-755039ed0313@kylinos.cn>
On Tue, Jan 27, 2026 at 05:33:10PM +0800, Feng Jiang wrote:
> On 2026/1/27 16:57, Andy Shevchenko wrote:
> > On Tue, Jan 27, 2026 at 09:25:54AM +0800, Feng Jiang wrote:
...
> >> +#define STRING_BENCH_BUF(test, buf_name, buf_size, func, ...) \
> >> +do { \
> >> + size_t buf_size, _bn_i, _bn_iters, _bn_size = 0; \
> >> + u64 _bn_t, _bn_mbps = 0, _bn_lat = 0; \
> >> + char *buf_name, *_bn_buf; \
> >> + \
> >> + _bn_buf = alloc_max_bench_buffer(test, bench_lens, \
> >> + ARRAY_SIZE(bench_lens), &_bn_size); \
> >> + KUNIT_ASSERT_NOT_ERR_OR_NULL(test, _bn_buf); \
> >> + \
> >> + fill_random_string(_bn_buf, _bn_size); \
> >> + \
> >> + for (_bn_i = 0; _bn_i < ARRAY_SIZE(bench_lens); _bn_i++) { \
> >> + buf_size = bench_lens[_bn_i]; \
> >> + buf_name = _bn_buf + _bn_size - buf_size - 1; \
> >> + _bn_iters = STRING_BENCH_WORKLOAD / max(buf_size, 1U); \
> >> + \
> >> + _bn_t = STRING_BENCH(_bn_iters, func, ##__VA_ARGS__); \
> >
> >> + \
> >
> > Remove unneeded blank line.
>
> Will fix.
>
> >> + if (_bn_t > 0) { \
> >> + _bn_mbps = (u64)(buf_size) * _bn_iters \
> >
> > Why buf_size in the parentheses here and not anywhere else (above)?
>
> It was a bit inconsistent. I'll remove the unneeded parentheses for buf_size.
>
> > I assume it's just an external temporary variable? But why do we need to have
> > it in the parameters to the macro?
>
> This is necessary because buf_size often needs to be passed as an argument
> to the function under test. For instance, when benchmarking strnlen, the
> caller must pass the current length as an argument:
> STRING_BENCH_BUF(test, buf, len, strnlen, buf, len);
Okay, and why is it needed in this macro? It get overridden immediately in
the loop. Assuming that the array size of bench lengths is not zero, this
has no visible use. Can you elaborate?
> >> + * (NSEC_PER_SEC / MEGA); \
> > > Leave '*' on the previous line.
>
> Will fix.
>
> >> + _bn_mbps = div64_u64(_bn_mbps, _bn_t); \
> >> + _bn_lat = div64_u64(_bn_t, _bn_iters); \
> >> + } \
> >> + kunit_info(test, "len=%zu: %llu MB/s (%llu ns/call)\n", \
> >> + buf_size, _bn_mbps, _bn_lat); \
> >> + } \
> >> +} while (0)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-27 9:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 1:25 [PATCH v5 0/8] riscv: optimize string functions and add kunit tests Feng Jiang
2026-01-27 1:25 ` [PATCH v5 1/8] lib/string_kunit: add correctness test for strlen() Feng Jiang
2026-01-28 22:39 ` Kees Cook
2026-01-29 2:19 ` Feng Jiang
2026-01-27 1:25 ` [PATCH v5 2/8] lib/string_kunit: add correctness test for strnlen() Feng Jiang
2026-01-27 1:25 ` [PATCH v5 3/8] lib/string_kunit: add correctness test for strrchr() Feng Jiang
2026-01-27 1:25 ` [PATCH v5 4/8] lib/string_kunit: add performance benchmark for strlen() Feng Jiang
2026-01-27 8:57 ` Andy Shevchenko
2026-01-27 9:33 ` Feng Jiang
2026-01-27 9:50 ` Andy Shevchenko [this message]
2026-01-28 1:44 ` Feng Jiang
2026-01-28 8:59 ` Andy Shevchenko
2026-01-28 9:20 ` Feng Jiang
2026-01-27 1:25 ` [PATCH v5 5/8] lib/string_kunit: extend benchmarks to strnlen() and chr searches Feng Jiang
2026-01-27 1:25 ` [PATCH v5 6/8] riscv: lib: add strnlen() implementation Feng Jiang
2026-01-27 1:25 ` [PATCH v5 7/8] riscv: lib: add strchr() implementation Feng Jiang
2026-01-27 1:25 ` [PATCH v5 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=aXiKelsJF-SiqnVS@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--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=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 \
--cc=sohil.mehta@intel.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