Messages in this thread | | | Date | Thu, 21 Jun 2007 14:16:35 +0200 | From | Ingo Molnar <> | Subject | Re: cpuset attach_task to touch per-cpu kernel threads? |
| |
* Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:
> But I am wondering if attach_task() should leave kernel threads alone > and act only upon user-space threads. Or maybe allow movement if it > doesn't result in changing kernel-threads's cpu affinity.
yeah, i'd agree with the latter. We could also special-case the migration thread to never be migrated itself. (although that's not the end of the matter either - two ksoftirqds on a cpu are not healty)
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/
| |