On Mon, Nov 10, 2014 at 12:16:51PM -0600, Tom Lendacky wrote: > Hi Herbert, > > Is the PCOMPRESS algorithm supposed to support asynchronous > implementations? In other words, are callers expected to handle the > -EINPROGRESS or -EAGAIN return codes that can be returned by an > asynchronous implementation? > > Or is it assumed that if the CRYPTO_ALG_ASYNC flag is not set then the > code path must be synchronous? If that's the case, should the pcompress > support be updated to look for synchronous implementations if the > CRYPTO_ALG_ASYNC flag isn't set or should asynchronous implementations > provide a synchronous fallback? The pcomp interface is entirely synchronous so for async support you'll have to create a new interface. pcomp is simply meant to replace the existing compress interface but unfortunately that job has not been completed as yet. 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
