Re: cpuset attach_task to touch per-cpu kernel threads?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Thursday, June 21, 2007 - 5:16 am

* Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:


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
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
cpuset attach_task to touch per-cpu kernel threads?, Srivatsa Vaddagiri, (Wed Jun 20, 6:49 pm)
Re: cpuset attach_task to touch per-cpu kernel threads?, Paul Jackson, (Wed Jun 20, 7:35 pm)
Re: cpuset attach_task to touch per-cpu kernel threads?, Ingo Molnar, (Thu Jun 21, 5:16 am)
Re: cpuset attach_task to touch per-cpu kernel threads?, Paul Jackson, (Thu Jun 21, 10:07 am)
Re: cpuset attach_task to touch per-cpu kernel threads?, Srivatsa Vaddagiri, (Thu Jun 21, 10:32 am)
Re: cpuset attach_task to touch per-cpu kernel threads?, Paul Jackson, (Thu Jun 21, 10:51 am)
Re: cpuset attach_task to touch per-cpu kernel threads?, Srivatsa Vaddagiri, (Fri Jun 22, 10:16 am)
Re: cpuset attach_task to touch per-cpu kernel threads?, Paul Jackson, (Fri Jun 22, 10:41 am)