[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a8137149a164a13a7a04d72b133ad3b@AcuMS.aculab.com>
Date: Mon, 13 Sep 2021 11:35:40 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Guo Ren' <guoren@...nel.org>, Palmer Dabbelt <palmer@...belt.com>
CC: Matteo Croce <mcroce@...ux.microsoft.com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Paul Walmsley <paul.walmsley@...ive.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>,
Bin Meng <bmeng.cn@...il.com>,
"Christoph Hellwig" <hch@...radead.org>
Subject: RE: [PATCH] riscv: use the generic string routines
> > These ended up getting rejected by Linus, so I'm going to hold off on
> > this for now. If they're really out of lib/ then I'll take the C
> > routines in arch/riscv, but either way it's an issue for the next
> > release.
> Agree, we should take the C routine in arch/riscv for common
> implementation. If any vendor what custom implementation they could
> use the alternative framework in errata for string operations.
I though the asm ones were significantly faster because
they were less affected by read latency.
(But they were horribly broken for misaligned transfers.)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists