[PATCH 35/35] pcrypt: use HIGHPRI and CPU_INTENSIVE workqueues for padata
in [Kernel]
|
Prev: Expose vendor-specific ACM channel on Nokia 5230
Next: [PATCH 07/35] workqueue: merge feature parameters into flags
From: Tejun Heo on 28 Jun 2010 17:10 pcrypt padata works are cpu intensive and shouldn't affect or be affected by workqueue concurrency management. Allocate padata workqueues with WQ_HIGHPRI and WQ_CPU_INTENSIVE flags set. Now that creating workqueues doesn't cost that much and less direct manipulation of workers is allowed, it might make sense to update padata interface such that it allocates workqueues with proper flags itself. Signed-off-by: Tejun Heo <tj(a)kernel.org> Cc: Herbert Xu <herbert(a)gondor.apana.org.au> Cc: David S. Miller <davem(a)davemloft.net> Cc: Steffen Klassert <steffen.klassert(a)secunet.com> --- crypto/pcrypt.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/crypto/pcrypt.c b/crypto/pcrypt.c index 247178c..4728cdc 100644 --- a/crypto/pcrypt.c +++ b/crypto/pcrypt.c @@ -385,11 +385,11 @@ static struct crypto_template pcrypt_tmpl = { static int __init pcrypt_init(void) { - encwq = create_workqueue("pencrypt"); + encwq = alloc_workqueue("pencrypt", WQ_HIGHPRI | WQ_CPU_INTENSIVE, 1); if (!encwq) goto err; - decwq = create_workqueue("pdecrypt"); + decwq = alloc_workqueue("pdecrypt", WQ_HIGHPRI | WQ_CPU_INTENSIVE, 1); if (!decwq) goto err_destroy_encwq; -- 1.6.4.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |