From: patchwork-bot+linux-riscv@kernel.org
To: Feng Jiang <jiangfeng@kylinos.cn>
Cc: linux-riscv@lists.infradead.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, herbert@gondor.apana.org.au,
samuel.holland@sifive.com, ajones@ventanamicro.com,
conor.dooley@microchip.com, charlie@rivosinc.com,
nathan@kernel.org, linusw@kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v7 0/8] riscv: optimize string functions and add kunit tests
Date: Fri, 03 Apr 2026 18:30:18 +0000 [thread overview]
Message-ID: <177524101803.1406513.15222599050806931246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130025018.172925-1-jiangfeng@kylinos.cn>
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 30 Jan 2026 10:50:10 +0800 you wrote:
> This series provides optimized implementations of strnlen(), strchr(),
> and strrchr() for the RISC-V architecture. The strnlen() implementation
> is derived from the existing optimized strlen(). For strchr() and
> strrchr(), the current versions use simple byte-by-byte assembly logic,
> which will serve as a baseline for future Zbb-based optimizations.
>
> The patch series is organized into three parts:
> 1. Correctness Testing: The first three patches add KUnit test cases
> for strlen(), strnlen(), and strrchr() to ensure the baseline and
> optimized versions are functionally correct.
> 2. Benchmarking Tool: Patches 4 and 5 extend string_kunit to include
> performance measurement capabilities, allowing for comparative
> analysis within the KUnit environment.
> 3. Architectural Optimizations: The final three patches introduce the
> RISC-V specific assembly implementations.
>
> [...]
Here is the summary with links:
- [v7,1/8] lib/string_kunit: add correctness test for strlen()
https://git.kernel.org/riscv/c/abd6819bbf5b
- [v7,2/8] lib/string_kunit: add correctness test for strnlen()
https://git.kernel.org/riscv/c/31a361f466a2
- [v7,3/8] lib/string_kunit: add correctness test for strrchr()
https://git.kernel.org/riscv/c/68768cdba710
- [v7,4/8] lib/string_kunit: add performance benchmark for strlen()
https://git.kernel.org/riscv/c/54a7a0ca4b60
- [v7,5/8] lib/string_kunit: extend benchmarks to strnlen() and chr searches
https://git.kernel.org/riscv/c/d52a2222768b
- [v7,6/8] riscv: lib: add strnlen() implementation
https://git.kernel.org/riscv/c/018ffd93d25f
- [v7,7/8] riscv: lib: add strchr() implementation
https://git.kernel.org/riscv/c/bf74efe28f7c
- [v7,8/8] riscv: lib: add strrchr() implementation
https://git.kernel.org/riscv/c/3dcf058583a1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Feng Jiang <jiangfeng@kylinos.cn>
Cc: linux-riscv@lists.infradead.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, herbert@gondor.apana.org.au,
samuel.holland@sifive.com, ajones@ventanamicro.com,
conor.dooley@microchip.com, charlie@rivosinc.com,
nathan@kernel.org, linusw@kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v7 0/8] riscv: optimize string functions and add kunit tests
Date: Fri, 03 Apr 2026 18:30:18 +0000 [thread overview]
Message-ID: <177524101803.1406513.15222599050806931246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130025018.172925-1-jiangfeng@kylinos.cn>
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 30 Jan 2026 10:50:10 +0800 you wrote:
> This series provides optimized implementations of strnlen(), strchr(),
> and strrchr() for the RISC-V architecture. The strnlen() implementation
> is derived from the existing optimized strlen(). For strchr() and
> strrchr(), the current versions use simple byte-by-byte assembly logic,
> which will serve as a baseline for future Zbb-based optimizations.
>
> The patch series is organized into three parts:
> 1. Correctness Testing: The first three patches add KUnit test cases
> for strlen(), strnlen(), and strrchr() to ensure the baseline and
> optimized versions are functionally correct.
> 2. Benchmarking Tool: Patches 4 and 5 extend string_kunit to include
> performance measurement capabilities, allowing for comparative
> analysis within the KUnit environment.
> 3. Architectural Optimizations: The final three patches introduce the
> RISC-V specific assembly implementations.
>
> [...]
Here is the summary with links:
- [v7,1/8] lib/string_kunit: add correctness test for strlen()
https://git.kernel.org/riscv/c/abd6819bbf5b
- [v7,2/8] lib/string_kunit: add correctness test for strnlen()
https://git.kernel.org/riscv/c/31a361f466a2
- [v7,3/8] lib/string_kunit: add correctness test for strrchr()
https://git.kernel.org/riscv/c/68768cdba710
- [v7,4/8] lib/string_kunit: add performance benchmark for strlen()
https://git.kernel.org/riscv/c/54a7a0ca4b60
- [v7,5/8] lib/string_kunit: extend benchmarks to strnlen() and chr searches
https://git.kernel.org/riscv/c/d52a2222768b
- [v7,6/8] riscv: lib: add strnlen() implementation
https://git.kernel.org/riscv/c/018ffd93d25f
- [v7,7/8] riscv: lib: add strchr() implementation
https://git.kernel.org/riscv/c/bf74efe28f7c
- [v7,8/8] riscv: lib: add strrchr() implementation
https://git.kernel.org/riscv/c/3dcf058583a1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-04-03 18:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 2:50 [PATCH v7 0/8] riscv: optimize string functions and add kunit tests Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 2:50 ` [PATCH v7 1/8] lib/string_kunit: add correctness test for strlen() Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 17:34 ` Kees Cook
2026-01-30 17:34 ` Kees Cook
2026-01-30 2:50 ` [PATCH v7 2/8] lib/string_kunit: add correctness test for strnlen() Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 17:34 ` Kees Cook
2026-01-30 17:34 ` Kees Cook
2026-01-30 2:50 ` [PATCH v7 3/8] lib/string_kunit: add correctness test for strrchr() Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 17:34 ` Kees Cook
2026-01-30 17:34 ` Kees Cook
2026-01-30 2:50 ` [PATCH v7 4/8] lib/string_kunit: add performance benchmark for strlen() Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 17:35 ` Kees Cook
2026-01-30 17:35 ` Kees Cook
2026-01-30 2:50 ` [PATCH v7 5/8] lib/string_kunit: extend benchmarks to strnlen() and chr searches Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 17:35 ` Kees Cook
2026-01-30 17:35 ` Kees Cook
2026-01-30 2:50 ` [PATCH v7 6/8] riscv: lib: add strnlen() implementation Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 2:50 ` [PATCH v7 7/8] riscv: lib: add strchr() implementation Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 2:50 ` [PATCH v7 8/8] riscv: lib: add strrchr() implementation Feng Jiang
2026-01-30 2:50 ` Feng Jiang
2026-01-30 17:37 ` [PATCH v7 0/8] riscv: optimize string functions and add kunit tests Kees Cook
2026-01-30 17:37 ` Kees Cook
2026-01-31 9:52 ` Andy Shevchenko
2026-01-31 9:52 ` Andy Shevchenko
2026-02-02 1:28 ` Feng Jiang
2026-02-02 1:28 ` Feng Jiang
2026-02-02 3:24 ` Feng Jiang
2026-02-02 3:24 ` Feng Jiang
2026-02-26 2:33 ` Feng Jiang
2026-02-26 2:33 ` Feng Jiang
2026-02-26 6:12 ` Feng Jiang
2026-02-26 6:12 ` Feng Jiang
2026-04-03 18:30 ` patchwork-bot+linux-riscv [this message]
2026-04-03 18:30 ` patchwork-bot+linux-riscv
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=177524101803.1406513.15222599050806931246.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.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=herbert@gondor.apana.org.au \
--cc=jiangfeng@kylinos.cn \
--cc=kees@kernel.org \
--cc=linusw@kernel.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.