From: Jisheng Zhang <jszhang@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: enable EFFICIENT_UNALIGNED_ACCESS and DCACHE_WORD_ACCESS
Date: Sat, 2 Dec 2023 19:28:10 +0800 [thread overview]
Message-ID: <ZWsUyjEx1fmXQEfW@xhacker> (raw)
In-Reply-To: <20231202111822.3569-1-jszhang@kernel.org>
On Sat, Dec 02, 2023 at 07:18:20PM +0800, Jisheng Zhang wrote:
> Some riscv implementations such as T-HEAD's C906, C908, C910 and C920
> supports efficient unaligned access, for performance reason we want
> to enable HAVE_EFFICIENT_UNALIGNED_ACCESS on these platforms. To
> avoid performance regressions on other non efficient unaligned access
> platforms, HAVE_EFFICIENT_UNALIGNED_ACCESS can't be globaly selected.
>
> To solve this problem, runtime code patching based on the detected
> speed is a good solution. But that's not easy, it involves lots of
> work to modify vairous subsystems such as net, mm, lib and so on.
> This can be done step by step.
Adding something as below here can make the series more clear:
So let's take an easier solution: add support to efficient unaligned
access and hide the support under NONPORTABLE.
>
> patch1 introduces RISCV_EFFICIENT_UNALIGNED_ACCESS which depends on
> NONPORTABLE, if users know during config time that the kernel will be
> only run on those efficient unaligned access hw platforms, they can
> enable it. Obviously, generic unified kernel Image should enable it.
typo: s/should/shouldn't
>
> patch2 adds support DCACHE_WORD_ACCESS when MMU and
> RISCV_EFFICIENT_UNALIGNED_ACCESS.
>
> Below test program and step shows how much performance can be improved:
>
> $ cat tt.c
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <unistd.h>
>
> #define ITERATIONS 1000000
>
> #define PATH "123456781234567812345678123456781"
>
> int main(void)
> {
> unsigned long i;
> struct stat buf;
>
> for (i = 0; i < ITERATIONS; i++)
> stat(PATH, &buf);
>
> return 0;
> }
>
> $ gcc -O2 tt.c
> $ touch 123456781234567812345678123456781
> $ time ./a.out
>
> Per my test on T-HEAD C910 platforms, the above test performance is
> improved by about 7.5%.
>
>
> Jisheng Zhang (2):
> riscv: introduce RISCV_EFFICIENT_UNALIGNED_ACCESS
> riscv: select DCACHE_WORD_ACCESS for efficient unaligned access HW
>
> arch/riscv/Kconfig | 13 +++++++++++
> arch/riscv/include/asm/asm-extable.h | 15 ++++++++++++
> arch/riscv/include/asm/word-at-a-time.h | 23 ++++++++++++++++++
> arch/riscv/mm/extable.c | 31 +++++++++++++++++++++++++
> 4 files changed, 82 insertions(+)
>
> --
> 2.42.0
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-12-02 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 11:18 [PATCH 0/2] riscv: enable EFFICIENT_UNALIGNED_ACCESS and DCACHE_WORD_ACCESS Jisheng Zhang
2023-12-02 11:18 ` [PATCH 1/2] riscv: introduce RISCV_EFFICIENT_UNALIGNED_ACCESS Jisheng Zhang
2023-12-02 11:18 ` [PATCH 2/2] riscv: select DCACHE_WORD_ACCESS for efficient unaligned access HW Jisheng Zhang
2023-12-03 11:53 ` Conor Dooley
2023-12-02 11:28 ` Jisheng Zhang [this message]
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=ZWsUyjEx1fmXQEfW@xhacker \
--to=jszhang@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@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