On Fri, 20 Sep 2013, Frederic Weisbecker wrote: > Now just for clarity, what do we then do with inline sofirq > executions: on local_bh_enable() for example, or explicit calls to > do_softirq() other than irq exit? Should we keep the current switch > to a different softirq stack? If we have a generic irq stack (used > for both hard and soft) that is big enough, perhaps we can also > switch to this generic irq stack for inline softirqs executions? > After all there is no much point in keeping a separate stack for > that: this result in cache misses if the inline softirq is > interrupted by a hardirq, also inlined softirqs can't happen in > hardirq, so there should be no much risk of overruns.
We can use the same irqstack for this because from the irqstack point of view, thats the same as if softirqs get executed from irq_exit(). Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/