Hi.
On Fri, Oct 24, 2008 at 03:16:52PM -0700, Loc Ho ([EMAIL PROTECTED]) wrote:
> I don't understand what you are referring to here. Let's assume that
> operation is submitted synchronously to cryptodev, cryptodev in turn will
> submit to the underlying driver. If the underlying driver is software based,
> it will completed synchronous and return without calling wait_for_completion.
> If the underlying driver is hardware based or asynchronous, it will wait for
> completion via the callback function signaling the event wait object. Now,
> let's assume that operation is submitted asynchronously to cryptodev, crypto
> in turn will submit to the underlying driver. If the underlying driver is
> software based and completed, it just return. If the underlying driver is
> asynchronous such as hardware, it will return immediately without waiting.
> CryptoDev will call the AIO callback function when the crypto driver call
> cryptodev callback function. Therefore, what is the issue?
With async driver crypto_ablkcipher_encrypt() (and other crypto
processing functions) will return immediately (with
-EINPROGRESS return value in case of HIFN driver for example),
but your code will wait for request completion at
wait_for_completion_interruptible() point.
--
Evgeniy Polyakov
--
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
