[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191122143102.vpsm5ryye2put2v2@gondor.apana.org.au>
Date: Fri, 22 Nov 2019 22:31:02 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Iuliana Prodan <iuliana.prodan@....com>
Cc: Horia Geanta <horia.geanta@....com>,
Aymen Sghaier <aymen.sghaier@....com>,
"David S. Miller" <davem@...emloft.net>,
Tom Lendacky <thomas.lendacky@....com>,
Gary Hook <gary.hook@....com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH 08/12] crypto: caam - support crypto_engine framework for
SKCIPHER algorithms
On Fri, Nov 22, 2019 at 02:11:46PM +0000, Iuliana Prodan wrote:
>
> So, just to be clear, I shouldn't use crypto_async_request in driver code?
> I see that this generic crypto request is used in multiple drivers.
I understand that a number of drivers do this in order to share
common code. However, this is definitely not the preferred way
of handling this. Ideally such code should be abstracted into
a higher layer such as crypto_engine so that the driver itself
never references these internal types.
> I can try sending _all_ requests to crypto engine and make some
> performance measurements to see which solution is best.
Thanks,
--
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