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

* Srivatsa Vaddagiri <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: cpuset attach_task to touch per-cpu kernel threads?
    • From: Paul Jackson <[email protected]>

• References:
  • cpuset attach_task to touch per-cpu kernel threads?
    • From: Srivatsa Vaddagiri <[email protected]>

• Prev by Date: Re: [PATCH RT] have x86_64 nmi watchdog also count irq 0
• Next by Date: Re: PROBLEM: PCI setup hangs on Asus Notebook (nolapic helps)
• Previous by thread: Re: cpuset attach_task to touch per-cpu kernel threads?
• Next by thread: Re: cpuset attach_task to touch per-cpu kernel threads?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]