[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 2 Feb 2021 09:27:33 +0000
From: "Alessandrelli, Daniele" <daniele.alessandrelli@...el.com>
To: "herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>
CC: "Khurana, Prabhjot" <prabhjot.khurana@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"Reshetova, Elena" <elena.reshetova@...el.com>,
"mgross@...ux.intel.com" <mgross@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"ardb@...nel.org" <ardb@...nel.org>,
"xuzaibo@...wei.com" <xuzaibo@...wei.com>,
"wangzhou1@...ilicon.com" <wangzhou1@...ilicon.com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"yumeng18@...wei.com" <yumeng18@...wei.com>
Subject: Re: [PATCH v7 4/7] crypto: add ecc curve and expose them
On Tue, 2021-02-02 at 16:13 +1100, Herbert Xu wrote:
> The issue is that we always require a software implementation for
> any given hardware algorithm. As otherwise kernel users cannot
> rely on the algorithm to work.
I understand. This sounds very reasonable to me.
> Of course we don't want to add every single algorithm out there
> to the kernel so that's why require there to be an actual in-kernel
> user before adding a given algorithm.
I see. Just to clarify: does the in-kernel user requirement also apply
to the case when the author of a device driver also provides the
software implementation for the new algorithms supported by device
driver / HW?
Powered by blists - more mailing lists