> ________________________________________ > From: Herbert Xu <[email protected]> > Sent: Wednesday, May 11, 2016 1:54 PM > To: Catalin Vasile > Cc: [email protected]; [email protected]; Horia > Ioan Geanta Neag; Alexandru Porosanu; Scott Wood > Subject: Re: [PATCH] crypto: caam: add backlogging support>
> On Wed, May 11, 2016 at 07:53:19AM +0000, Catalin Vasile wrote: > > > > Every request will be queued and eventually done. > > The hardware equipment has a constraint on the number of tfms it can have. > > Is there a requirement to support an infinite number of tfms on a device? > > > > > You should use a software queue instead.>> > As I said you drivers are always supposed to have a software queue > in addition to any hardware queues. There is no reason why your > driver should be special in this regard.> Hi Herbert, We are inclining towards a hardware backlogging solution because on low end devices the software queue does not scale very well. Regarding your concerns, we are now evaluating adding a software queue based fallback solution: if the hardware backlogging fails because no hardware slots are available, backlog the job inside a crypto software queue. Is this hybrid configurable solution acceptable? Namely, if the hardware queue is full, to fallback to the crypto software queue. > Cheers, > -- > Email: Herbert Xu <[email protected]> > Home Page: http://gondor.apana.org.au/~herbert/ > PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
