Re: [RFC] per-CPU cryptd thread implementation based on workqueue

On Mon, Feb 02, 2009 at 11:30:25AM +0800, Huang Ying wrote: The only needed spin lock usage is cryptd_tfm_in_queue() now, I think we can protect that via RCU, what's your opinions? We should just get rid of cryptd_tfm_in_queue since it's only used for debugging. But I think the simplest

[PATCH 3/3] crypto: Uses kcrypto_wq instead of keventd_wq in chainiv

keventd_wq has potential starvation problem, so use dedicated kcrypto_wq instead. Signed-off-by: Huang Ying ying.hu...@intel.com --- crypto/Kconfig |1 + crypto/chainiv.c |3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) --- a/crypto/Kconfig +++ b/crypto/Kconfig @@ -56,6 +56,7

[PATCH 1/3] crypto: Use dedicated workqueue for crypto subsystem

A dedicated workqueue named kcrypto_wq is created to be used by crypto subsystem. The system shared keventd_wq is not suitable for encryption/decryption, because of potential starvation problem. Signed-off-by: Huang Ying ying.hu...@intel.com --- crypto/Kconfig |3 +++