From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>
Cc: "conor.dooley@microchip.com" <conor.dooley@microchip.com>,
"ajones@ventanamicro.com" <ajones@ventanamicro.com>,
"samuel@sholland.org" <samuel@sholland.org>,
"alexghiti@rivosinc.com" <alexghiti@rivosinc.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>
Subject: Re: [PATCH] riscv: lib: Optimize 'strlen' function
Date: Mon, 18 Dec 2023 01:41:33 +0000 [thread overview]
Message-ID: <de80b4c7-1ffb-478e-9117-9d5b829470bd@gmail.com> (raw)
In-Reply-To: <86d3947bce1f49c395224998e7d65dc2@AcuMS.aculab.com>
On 12/17/23 17:00, David Laight wrote:
> I'd also guess that pretty much all the calls in-kernel are short.
> You might try counting as: histogram[ilog2(strlen_result)]++
> and seeing what it shows for some workload.
> I bet you (a beer if I see you!) that you won't see many over 1k.
Hi David,
Here is the statistics for strlen result:
[ 223.169575] Calls count for 2^0: 6150
[ 223.173293] Calls count for 2^1: 184852
[ 223.177142] Calls count for 2^2: 313896
[ 223.180990] Calls count for 2^3: 185844
[ 223.184881] Calls count for 2^4: 87868
[ 223.188660] Calls count for 2^5: 9916
[ 223.192368] Calls count for 2^6: 1865
[ 223.196062] Calls count for 2^7: 0
[ 223.199483] Calls count for 2^8: 0
[ 223.202952] Calls count for 2^9: 0
...
Looks like I've just lost a beer :)
Considering this statistics, I'd say implementing the word-oriented
strlen is an overcomplication - we wouldn't get any performance gain and
it just doesn't worth it.
I simplified your code a little bit, it looks like the alignment there
is unnecessary: QEMU test shows the same performance independently from
alignment. Tests on the board gave the same result (perhaps because the
CPU on the board has 2 DDR channels?)
mv t0, a0
1:
lbu t1, 0(a0)
lbu t2, 1(a0)
addi a0, a0, 2
beqz t1, 2f
bnez t2, 1b
addi a0, a0, 1
2:
addi a0, a0, -2
sub a0, a0, t0
ret
If it looks good to you, would you mind if I send the patch with it?
Could I add you to suggested-by tag?
--
Kind regards,
Ivan Orlov
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-12-18 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 15:45 [PATCH] riscv: lib: Optimize 'strlen' function Ivan Orlov
2023-12-17 17:00 ` David Laight
2023-12-17 22:52 ` Ivan Orlov
2023-12-18 1:41 ` Ivan Orlov [this message]
2023-12-18 9:20 ` David Laight
2023-12-18 10:03 ` Ivan Orlov
2023-12-18 10:12 ` David Laight
2023-12-17 18:10 ` David Laight
2023-12-17 23:23 ` Ivan Orlov
2023-12-18 9:12 ` 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=de80b4c7-1ffb-478e-9117-9d5b829470bd@gmail.com \
--to=ivan.orlov0322@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel@sholland.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).