From: Michal Hocko <mhocko@suse.cz>
To: Li Zefan <lizefan@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Glauber Costa <glommer@parallels.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/8] cgroup: implement cgroup_is_ancestor()
Date: Mon, 8 Apr 2013 20:03:44 +0200 [thread overview]
Message-ID: <20130408180335.GA22512@dhcp22.suse.cz> (raw)
In-Reply-To: <20130408144750.GK17178@dhcp22.suse.cz>
On Mon 08-04-13 16:47:50, Michal Hocko wrote:
> On Mon 08-04-13 16:20:11, Li Zefan wrote:
> [...]
> > @@ -5299,6 +5300,26 @@ struct cgroup_subsys_state *cgroup_css_from_dir(struct file *f, int id)
> > return css ? css : ERR_PTR(-ENOENT);
> > }
> >
> > +/**
> > + * cgroup_is_ancestor - test "root" cgroup is an ancestor of "child"
> > + * @child: the cgroup to be tested.
> > + * @root: the cgroup supposed to be an ancestor of the child.
> > + *
> > + * Returns true if "root" is an ancestor of "child" in its hierarchy.
> > + */
> > +bool cgroup_is_ancestor(struct cgroup *child, struct cgroup *root)
> > +{
> > + int depth = child->depth;
>
> Is this functionality helpful for other controllers but memcg?
> css_is_ancestor is currently used only by memcg code AFAICS and we can
> get the same functionality easily by using something like:
And as it turned out using css_is_ancestor is not correct. Here
is a patch to fix the issue. I will leave the decision whether
cgroup_is_ancestor makes sense even without users to you.
Would you be willing to take this into your current series so that we to
not clash over that code?
---
next prev parent reply other threads:[~2013-04-08 18:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 8:19 [PATCH 0/8] memcg, cgroup: kill css_id Li Zefan
2013-04-08 8:20 ` [PATCH 1/8] cgroup: implement cgroup_is_ancestor() Li Zefan
2013-04-08 14:47 ` Michal Hocko
2013-04-08 15:57 ` Tejun Heo
2013-04-08 16:33 ` Michal Hocko
2013-04-08 18:03 ` Michal Hocko [this message]
2013-04-08 21:36 ` Tejun Heo
2013-04-09 6:42 ` Michal Hocko
2013-04-08 15:39 ` Tejun Heo
2013-04-09 3:21 ` Kamezawa Hiroyuki
2013-04-09 3:29 ` Li Zefan
2013-04-08 8:20 ` [PATCH 2/8] cgroup: implement cgroup_from_id() Li Zefan
2013-04-08 15:43 ` Tejun Heo
2013-04-09 3:12 ` Li Zefan
2013-04-08 15:48 ` Tejun Heo
2013-04-09 3:56 ` Kamezawa Hiroyuki
2013-04-09 4:08 ` Kamezawa Hiroyuki
2013-04-08 8:21 ` [PATCH 3/8] memcg: convert to use cgroup_is_ancestor() Li Zefan
2013-04-09 3:58 ` Kamezawa Hiroyuki
2013-04-09 6:49 ` Michal Hocko
2013-04-08 8:21 ` [PATCH 4/8] memcg: convert to use cgroup_from_id() Li Zefan
2013-04-08 14:53 ` Michal Hocko
2013-04-09 3:00 ` Li Zefan
2013-04-09 3:59 ` Kamezawa Hiroyuki
2013-04-08 8:22 ` [PATCH 5/8] memcg: convert to use cgroup->id Li Zefan
2013-04-08 14:57 ` Michal Hocko
2013-04-09 3:02 ` Li Zefan
2013-04-09 6:49 ` Michal Hocko
2013-04-09 4:02 ` Kamezawa Hiroyuki
2013-04-08 8:22 ` [PATCH 6/8] memcg: fail to create cgroup if the cgroup id is too big Li Zefan
2013-04-08 15:01 ` Michal Hocko
2013-04-08 8:23 ` [PATCH 7/8] memcg: don't use css_id any more Li Zefan
2013-04-08 15:01 ` Michal Hocko
2013-04-09 4:11 ` Kamezawa Hiroyuki
2013-04-08 8:23 ` [PATCH 8/8] cgroup: kill css_id Li Zefan
2013-04-08 15:51 ` Tejun Heo
2013-04-08 14:37 ` [PATCH 0/8] memcg, " Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130408180335.GA22512@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).