[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140415165221.GD30990@htj.dyndns.org>
Date: Tue, 15 Apr 2014 12:52:21 -0400
From: Tejun Heo <tj@...nel.org>
To: Li Zefan <lizefan@...wei.com>
Cc: containers@...ts.linux-foundation.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, john@...nmccutchan.com,
rlove@...ve.org, eparis@...isplace.org, gregkh@...uxfoundation.org,
serge.hallyn@...ntu.com, lennart@...ttering.net, kay@...y.org
Subject: Re: [PATCH 3/3] cgroup: implement cgroup.subtree_populated for the
default hierarchy
On Tue, Apr 15, 2014 at 10:54:50AM -0400, Tejun Heo wrote:
> Hello,
>
> On Tue, Apr 15, 2014 at 08:57:21AM +0800, Li Zefan wrote:
> > Is cgroup.tree_populated a better name?
> >
> > cgroup.subtree_control controls child cgroups only, but .subtree_populated
> > shows 1 if there're tasks in the cgroup or its children, so the two
> > are a bit inconsistent to me.
>
> Yes, good catch. subtree_control affects subtree proper.
> subtree_populated covers self too. The difference is subtle and the
> trade off between shared pattern in names and clarifying the subtlety
> didn't seem clear-cut to me. Hmmm....
How about cgroup.populated?
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists