On Mon, Jun 15, 2015 at 01:38:53PM +0200, Boris Brezillon wrote:

Oh right.
I still have trouble understanding the need for the backlog concept
(maybe you can give some insight): the backlog is just another list
where we put all the requests when the queue has exceeded the limit
fixed in crypto_queue_init, but the result is pretty much the same, the
request stored in the backlog will be handled at some point, so what's
the real point of this backlog.

The point is to tell the user to stop sending requests by returning
EBUSY.  When the queue clears up again we then invoke the callback
and tell the user that they can send requests again.

Cheers,
-- 
Email: Herbert Xu [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt