From: Qingfang Deng <dqfext@gmail.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,
ardb@kernel.org, charlie@rivosinc.com,
conor.dooley@microchip.com, ajones@ventanamicro.com,
linus.walleij@linaro.org, nathan@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH v3 6/8] riscv: lib: add strnlen implementation
Date: Wed, 21 Jan 2026 15:24:38 +0800 [thread overview]
Message-ID: <20260121072438.6646-1-dqfext@gmail.com> (raw)
In-Reply-To: <20260120065852.166857-7-jiangfeng@kylinos.cn>
On Tue, 20 Jan 2026 14:58:50 +0800, Feng Jiang wrote:
> diff --git a/arch/riscv/lib/strnlen.S b/arch/riscv/lib/strnlen.S
Branches that test maxlen can be replaced with Zbb minu instruction.
(see below)
> + /*
> + * Returns
> + * a0 - String length
> + *
> + * Parameters
> + * a0 - String to measure
> + * a1 - Max length of string
> + *
> + * Clobbers
> + * t0, t1, t2, t3, t4
> + */
> +
> + /* If maxlen is 0, return 0. */
> + beqz a1, 3f
> +
> + /* Number of irrelevant bytes in the first word. */
> + andi t2, a0, SZREG-1
> +
> + /* Align pointer. */
> + andi t0, a0, -SZREG
> +
> + li t3, SZREG
> + sub t3, t3, t2
> + slli t2, t2, 3
> +
> + /* Aligned boundary. */
> + add t4, a0, a1
> + andi t4, t4, -SZREG
> +
> + /* Get the first word. */
> + REG_L t1, 0(t0)
> +
> + /*
> + * Shift away the partial data we loaded to remove the irrelevant bytes
> + * preceding the string with the effect of adding NUL bytes at the
> + * end of the string's first word.
> + */
> + SHIFT t1, t1, t2
> +
> + /* Convert non-NUL into 0xff and NUL into 0x00. */
> + orc.b t1, t1
> +
> + /* Convert non-NUL into 0x00 and NUL into 0xff. */
> + not t1, t1
> +
> + /*
> + * Search for the first set bit (corresponding to a NUL byte in the
> + * original chunk).
> + */
> + CZ t1, t1
> +
> + /*
> + * The first chunk is special: compare against the number
> + * of valid bytes in this chunk.
> + */
> + srli a0, t1, 3
> +
> + /* Limit the result by maxlen. */
> + bleu a1, a0, 3f
minu a0, a0, a1
> +
> + bgtu t3, a0, 2f
> +
> + /* Prepare for the word comparison loop. */
> + addi t2, t0, SZREG
> + li t3, -1
> +
> + /*
> + * Our critical loop is 4 instructions and processes data in
> + * 4 byte or 8 byte chunks.
> + */
> + .p2align 3
> +1:
> + REG_L t1, SZREG(t0)
> + addi t0, t0, SZREG
> + orc.b t1, t1
> + bgeu t0, t4, 4f
> + beq t1, t3, 1b
> +4:
> + not t1, t1
> + CZ t1, t1
> + srli t1, t1, 3
> +
> + /* Get number of processed bytes. */
> + sub t2, t0, t2
> +
> + /* Add number of characters in the first word. */
> + add a0, a0, t2
> +
> + /* Add number of characters in the last word. */
> + add a0, a0, t1
> +
> + /* Ensure the final result does not exceed maxlen. */
> + bgeu a0, a1, 3f
minu a0, a0, a1
> +2:
> + ret
> +3:
> + mv a0, a1
> + ret
> +
> +.option pop
--
Qingfang
_______________________________________________
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-21 7:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 6:58 [PATCH v3 0/8] riscv: optimize string functions and add kunit tests Feng Jiang
2026-01-20 6:58 ` [PATCH v3 1/8] lib/string_kunit: add correctness test for strlen Feng Jiang
2026-01-20 7:28 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 2/8] lib/string_kunit: add correctness test for strnlen Feng Jiang
2026-01-20 7:29 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 3/8] lib/string_kunit: add correctness test for strrchr() Feng Jiang
2026-01-20 7:30 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 4/8] lib/string_kunit: add performance benchmarks for strlen Feng Jiang
2026-01-20 7:46 ` Andy Shevchenko
2026-01-21 5:45 ` Feng Jiang
2026-01-20 6:58 ` [PATCH v3 5/8] lib/string_kunit: extend benchmarks to strnlen and chr searches Feng Jiang
2026-01-20 7:48 ` Andy Shevchenko
2026-01-21 5:48 ` Feng Jiang
2026-01-20 6:58 ` [PATCH v3 6/8] riscv: lib: add strnlen implementation Feng Jiang
2026-01-20 7:31 ` Andy Shevchenko
2026-01-21 5:52 ` Feng Jiang
2026-01-21 7:24 ` Qingfang Deng [this message]
2026-01-23 1:28 ` Feng Jiang
2026-01-20 6:58 ` [PATCH v3 7/8] riscv: lib: add strchr implementation Feng Jiang
2026-01-20 7:31 ` Andy Shevchenko
2026-01-20 6:58 ` [PATCH v3 8/8] riscv: lib: add strrchr implementation Feng Jiang
2026-01-20 7:32 ` Andy Shevchenko
2026-01-20 7:36 ` [PATCH v3 0/8] riscv: optimize string functions and add kunit tests Andy Shevchenko
2026-01-21 6:44 ` Feng Jiang
2026-01-21 7:01 ` Andy Shevchenko
2026-01-21 8:12 ` Feng Jiang
2026-01-21 10:57 ` David Laight
2026-01-23 3:12 ` Feng Jiang
2026-01-23 10:16 ` David Laight
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=20260121072438.6646-1-dqfext@gmail.com \
--to=dqfext@gmail.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=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=ebiggers@kernel.org \
--cc=jiangfeng@kylinos.cn \
--cc=joel@jms.id.au \
--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 \
/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