Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > > Why would the driver return EBUSY from an async API? What's the caller > supposed to do with that? The Crypto API offers two modes for callers to deal with congestion. If the request can be safely dropped (e.g., IPsec) then ENOSPC will be returned and should be dealt with accordingly. If the request cannot be dropped then EBUSY is returned to indicate congestion, and the caller must refrain from issuing any more requests until the Crypto API signals that there is space for them. The request flag CRYPTO_TFM_REQ_MAY_BACKLOG is used to indicate which mode you wish to use. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
