On Tue, 15 Feb 2005, Andrew Morton wrote: > Zwane Mwaikambo <[EMAIL PROTECTED]> wrote: > > > > Ensure that we only offline the processor when it's safe and never run > > softirqs in another processor's ksoftirqd context. This also gets rid of > > the warnings in ksoftirqd on cpu offline. > > I don't get it. ksoftirqd is pinned to its cpu, so why does any of this > matter?
We take down ksoftirqds at CPU_DEAD time, so there is a brief period whereupon there is a ksoftirqd thread for an offline processor, it is at this point that ->cpus_allowed won't have it pinned anymore. An online processor would then take down that ksoftirqd and exit it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
