[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZmfBxLB8RC_KNUlx@gondor.apana.org.au>
Date: Tue, 11 Jun 2024 11:17:24 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Kamlesh Gurudasani <kamlesh@...com>, kristo@...nel.org, will@...nel.org,
akpm@...ux-foundation.org, davem@...emloft.net,
mcoquelin.stm32@...il.com, alexandre.torgue@...s.st.com,
robh@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, vigneshr@...com, catalin.marinas@....com,
linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 0/6] Add support for MCRC64 engine to calculate 64-bit
CRC in Full-CPU mode
On Mon, Jun 10, 2024 at 08:13:14PM -0700, Eric Biggers wrote:
>
> I thought the rule is that there needs to be an in-kernel user to add algorithms
> to the crypto API? Is there any precedent for adding new algorithms purely so
> that accelerators that implement them can be accessed from userspace via AF_ALG?
I agree. Perhaps this driver could instead be added as a simple
char device that is then used directly by the intended user without
going through the Crypto API at all.
That would make it a lot simpler.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists