From: Steffen Klassert <steffen.klass...@secunet.com> Date: Thu, 8 Oct 2009 09:28:18 +0200
> diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h > index 1af1e4b..6bc5dde 100644 > --- a/include/linux/interrupt.h > +++ b/include/linux/interrupt.h > @@ -350,6 +350,8 @@ enum > TASKLET_SOFTIRQ, > SCHED_SOFTIRQ, > HRTIMER_SOFTIRQ, > + AEAD_ENC_SOFTIRQ, > + AEAD_DEC_SOFTIRQ, > PADATA_SOFTIRQ, > RCU_SOFTIRQ, /* Preferable RCU should always be the last softirq */ > Steffen are we going to end up adding a softirq for every crypto transform type? That won't work, softirqs are to be scarcely allocated and operate at a very high level. I can think of two alternatives: 1) One softirq that does per-cpu padata work via some generic callout mechanism. 2) Use tasklets Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
