[PATCH RFC 00/10] crypto: engine: permit to batch requests
clabbe.montjoie at gmail.com
Thu Jan 16 05:16:03 PST 2020
On Thu, Jan 16, 2020 at 11:33:24AM +0000, Iuliana Prodan wrote:
> On 1/14/2020 3:59 PM, Corentin Labbe wrote:
> > Hello
> > The sun8i-ce hardware can work on multiple requests in one batch.
> > For this it use a task descriptor, and chain them.
> > For the moment, the driver does not use this mechanism and do requests
> > one at a time and issue an irq for each.
> > Using the chaning will permit to issue less interrupts, and increase
> > thoughput.
> > But the crypto/engine can enqueue lots of requests but can ran them only
> > one by one.
> > This serie introduce a way to batch requests in crypto/engine by
> > - setting a batch limit (1 by default)
> > - refactor the prepare/unprepare code to permit to have x requests
> > prepared/unprepared at the same time.
> > For testing the serie, the selftest are not enough, since it issue
> > request one at a time.
> > I have used LUKS for testing it.
> > Please give me what you think about this serie, specially maintainers
> > which have hardware with the same kind of capability.
> I'm working on CAAM, on adding support for crypto-engine.
> These modifications are not working on CAAM.
> They seem to be specific to requests that are linked. CAAM can work on
> multiple request, at the same time, but they are processed independently.
> So, I believe the parallelization is a good idea, but the requests still
> need to be independent.
> I'll follow up with comments on each patch.
Thanks for the review.
Yes my serie is for doing "linked" request.
For the CAAM, if you can do multiple request independently, why not having x crypto engine ? (like sun8i-ce/sun8i-ss/amlogic)
> Also, IMO you should send the patches for crypto-engine improvements in
> a separate series from the one for allwinner driver.
For this RFC serie, I tried to do real atomic patch, for let people see the whole process.
More information about the linux-arm-kernel