Re: [PATCH v2] crypto/caam: add backlogging support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Sep 18, 2015 at 02:07:38PM +0000, Porosanu Alexandru wrote:
> 
> MAY_BACKLOG requests will fail once you run out of memory (f.i. backlogging using crypto_queue)
> Now, for this patch requests will be dropped if there are no more "backlogging" slots available.
> Would limiting the # of tfms w/MAY_BACKLOG associated with the driver to the # of backlogging slots be OK?

Sure running out of memory is obviously a good reason to fail
a request.  But if you still have memory MAY_BACKLOG must not
fail.

Each tfm must be able to submit at least one MAY_BACKLOG request,
that's the whole point of this flag.  It's used for disk encryption
where failing is not an option.

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



[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux