Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-05-05 Thread Raghavendra KT
On 5/2/14, Tejun Heo wrote: > Hello, > > On Wed, Apr 30, 2014 at 04:27:51PM +0530, Raghavendra KT wrote: [...] >> Because all the way along, though we have freedom to make the cpusets >> exclusive and move tasks (say VMs) into them, >> making sure they do not interfere with each other, we can not

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-05-02 Thread Tejun Heo
Hello, On Wed, Apr 30, 2014 at 04:27:51PM +0530, Raghavendra KT wrote: > For some controllers like cpuset, when we have exclusive_cpu is set, > what about having a knob in the cpuset controller > to move the task to non-root (when option is set). I'm doubtful. > Because all the way along, though

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-30 Thread Raghavendra KT
On Mon, Apr 14, 2014 at 11:22 PM, Tejun Heo wrote: >> How does this work for root's tasks now? Given that task can only be >> in leaf cgroups, that means tasks can't be in / cgroup (If one wants >> to create some cgroups). Does that mean / will be empty and init system >> need to setup things righ

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Tejun Heo
Hello, On Tue, Apr 15, 2014 at 10:58:24AM +0800, Li Zefan wrote: > I know we should allow multiple hierarchies, but why we allow this even > if sane_behavior is specified? Oh, because we didn't have unified hierarchy before. The whole sane_behavior thing is gonna go away. It'll be absorbed into

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Li Zefan
on 2014/4/15 3:21, Tejun Heo wrote: > Hello, > > On Mon, Apr 14, 2014 at 02:14:21PM -0400, Vivek Goyal wrote: >> So is this an intermediate mode before we move to single hiearchy *only* >> mode. AFAIK, you had mentioned that we will support legacy multiple >> hiearchy mode but single hiearchy is t

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Tejun Heo
On Thu, Mar 27, 2014 at 10:40:49PM -0400, Tejun Heo wrote: > The patchset is on top of cgroup/for-3.15 01a971406177 ("cgroup: Use > RCU_INIT_POINTER(x, NULL) in cgroup.c") and also available in the > following git branch. > > git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-unif

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Tejun Heo
Hello, On Mon, Apr 14, 2014 at 02:14:21PM -0400, Vivek Goyal wrote: > So is this an intermediate mode before we move to single hiearchy *only* > mode. AFAIK, you had mentioned that we will support legacy multiple > hiearchy mode but single hiearchy is the new default mode. Hmmm? It's a separate

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Vivek Goyal
On Mon, Apr 14, 2014 at 01:52:36PM -0400, Tejun Heo wrote: > Hello, > > On Mon, Apr 14, 2014 at 11:45:56AM -0400, Vivek Goyal wrote: > > So this patchset does not *enforce* a single hierarchy? So user space > > can still mount other hierarchies. > > Nope, nothing is forced. Controllers may be mo

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Tejun Heo
Hello, On Mon, Apr 14, 2014 at 11:45:56AM -0400, Vivek Goyal wrote: > So this patchset does not *enforce* a single hierarchy? So user space > can still mount other hierarchies. Nope, nothing is forced. Controllers may be moved between unified and traditional multiple hierarchies. > How does thi

Re: [PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-04-14 Thread Vivek Goyal
On Thu, Mar 27, 2014 at 10:40:49PM -0400, Tejun Heo wrote: [..] > This patchset finally implements the default unified hierarchy. The > goal is providing enough flexibility while enforcing stricter common > structure where appropriate to address the above listed issues. > > Controllers which are

[PATCHSET cgroup/for-3.15] cgroup: implement unified hierarchy

2014-03-27 Thread Tejun Heo
Hello, (this is too late for the upcoming merge window and is targeting the next devel cycle) cgroup currently allows creating arbitrary number of hierarchies and any number of controllers may be associated with a given tree. This allows for huge amount of variance how tasks are associated with