[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEUhbmUjht1ss+Z0a-kWYdn_Lk6TCzQhvxcD1FgJb0svmvhg1A@mail.gmail.com>
Date: Tue, 15 Jun 2021 10:43:18 +0800
From: Bin Meng <bmeng.cn@...il.com>
To: Matteo Croce <mcroce@...ux.microsoft.com>
Cc: linux-riscv <linux-riscv@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-arch@...r.kernel.org,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Atish Patra <atish.patra@....com>,
Emil Renner Berthing <kernel@...il.dk>,
Akira Tsukamoto <akira.tsukamoto@...il.com>,
Drew Fustini <drew@...gleboard.org>
Subject: Re: [PATCH 0/3] riscv: optimized mem* functions
Hi Matteo,
On Tue, Jun 15, 2021 at 10:39 AM Matteo Croce
<mcroce@...ux.microsoft.com> wrote:
>
> From: Matteo Croce <mcroce@...rosoft.com>
>
> Replace the assembly mem{cpy,move,set} with C equivalent.
>
> Try to access RAM with the largest bit width possible, but without
> doing unaligned accesses.
>
> Tested on a BeagleV Starlight with a SiFive U74 core, where the
> improvement is noticeable.
>
There is already a patch on the ML for optimizing the assembly version.
https://patchwork.kernel.org/project/linux-riscv/patch/20210216225555.4976-1-gary@garyguo.net/
Would you please try that and compare the results?
Regards,
Bin
Powered by blists - more mailing lists