|
|
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Fri, 20 Apr 2012, Peter Zijlstra wrote: > On Fri, 2012-04-20 at 08:42 -0700, Tejun Heo wrote: > > I'm still leaning towards restricting kthreadd and any PF_THREAD_BOUND > > threads in the root cgroup. > > I'd definitely agree with restricting those. > > > I'm not sure about !BOUND kthreads tho. > > It doesn't make sense for the most part but there are cases > > (e.g. crypto kthreads) which might make some sense. > > > Agreed as well. There are a few nasty corner cases with unbound > workqueues vs allowing cgroups (as how to place new worker threads > correctly etc..). Sorting that is a 'fun' next problem. > > Could we merge the kthreadd/PF_THREAD_BOUND restriction? You've got my > ACK and I'm fairly sure tglx will ACK it as well. Acked-and-appreciated-by-me -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Kernel] [Kernel Newbies] [x86 Platform Driver] [Share Photos] [Security] [Netfilter] [Bugtraq] [Linux FS] [Photo] [Yosemite] [Yosemite Discussion] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]
![]() |