> an irq that could mark the softirq active under entry.S will also run
> do_softirq itself before iret to entry.S. [...]
yep.
> [...] If the softirq remains active after an irq it it because it was
> marked active again under do_softirq and ksoftirq is the way to go for
> fixing that case I think.
i took at look at your ksoftirq stuff yesterday, and i think it's
completely unnecessery and adds serious overhead to softirq handling. The
whole point of softirqs is to have maximum scalability and no
serialization. Why did you add ksoftirqd, would you mind explaining it?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/