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? Thanks, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
