On Tue, Nov 11, 2014 at 08:04:03PM +0200, Nicolae Rosia wrote: > On Fri, May 30, 2014 at 4:41 PM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > wrote: > > > [...] > > This is because the user is supposed to back off once they get > > EBUSY, until they're notified once the backlog entry is popped > > off (but not processed, it must be resubmitted). > > [...] > > > > I'm trying to understand the backlog mechanism and after reading the source > of crypto_enqueue_request and Stephan Mueller's example [1], my > understanding is that the user does not have to queue again the backlogged > request because when it returned -EBUSY it was added to the > crypto_queue->list. Am I missing something? You're right, the backlogged request does not need to be resubmitted. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
