[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0402MB348517DB62AA6A1C1A137FE7981B0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Date: Wed, 12 Feb 2020 18:52:37 +0000
From: Horia Geanta <horia.geanta@....com>
To: Iuliana Prodan <iuliana.prodan@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Aymen Sghaier <aymen.sghaier@....com>
CC: "David S. Miller" <davem@...emloft.net>,
Silvano Di Ninno <silvano.dininno@....com>,
Franck Lenormand <franck.lenormand@....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 v6 6/9] crypto: caam - support crypto_engine framework for
SKCIPHER algorithms
On 2/12/2020 7:56 PM, Iuliana Prodan wrote:
> Integrate crypto_engine into CAAM, to make use of the engine queue.
> Add support for SKCIPHER algorithms.
>
> This is intended to be used for CAAM backlogging support.
> The requests, with backlog flag (e.g. from dm-crypt) will be listed
> into crypto-engine queue and processed by CAAM when free.
> This changes the return codes for enqueuing a request:
> -EINPROGRESS if OK, -EBUSY if request is backlogged (via
> crypto-engine), -ENOSPC if the queue is full, -EIO if it
> cannot map the caller's descriptor.
>
> The requests, with backlog flag, will be listed into crypto-engine
> queue and processed by CAAM when free. Only the backlog request are
> sent to crypto-engine since the others can be handled by CAAM, if free,
> especially since JR has up to 1024 entries (more than the 10 entries
> from crypto-engine).
>
> Signed-off-by: Iuliana Prodan <iuliana.prodan@....com>
> Signed-off-by: Franck LENORMAND <franck.lenormand@....com>
Reviewed-by: Horia Geantă <horia.geanta@....com>
Thanks,
Horia
Powered by blists - more mailing lists