From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: <containers@lists.linux-foundation.org>,
<cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kay@vrfy.org>, <greg@kroah.com>, <lennart@poettering.net>,
<daniel@zonque.org>
Subject: Re: [PATCHSET] cgroup: implement task_cgroup_path_from_hierarchy()
Date: Mon, 15 Apr 2013 11:43:55 +0800 [thread overview]
Message-ID: <516B777B.9050704@huawei.com> (raw)
In-Reply-To: <1365964619-14762-1-git-send-email-tj@kernel.org>
On 2013/4/15 2:36, Tejun Heo wrote:
> kdbus folks want a sane way to determine the cgroup path that a given
> task belongs to on a given hierarchy, which is a reasonble thing to
> expect from cgroup core.
>
> This patchset make hierarchy_id allocation use idr instead of ida and
> implement task_cgroup_path_from_hierarchy(). In the process, the
> yucky ida cyclic allocation is replaced with idr_alloc_cyclic().
>
> 0001-cgroup-refactor-hierarchy_id-handling.patch
> 0002-cgroup-drop-hierarchy_id_lock.patch
> 0003-cgroup-make-hierarchy_id-use-cyclic-idr.patch
> 0004-cgroup-implement-task_cgroup_path_from_hierarchy.patch
>
> 0001-0002 prepare for conversion to idr, which 0003 does.
>
> 0004 implements the new function.
>
Acked-by: Li Zefan <lizefan@huawei.com>
next prev parent reply other threads:[~2013-04-15 3:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 18:36 [PATCHSET] cgroup: implement task_cgroup_path_from_hierarchy() Tejun Heo
2013-04-14 18:36 ` [PATCH 1/4] cgroup: refactor hierarchy_id handling Tejun Heo
2013-04-14 18:36 ` [PATCH 2/4] cgroup: drop hierarchy_id_lock Tejun Heo
2013-04-14 18:36 ` [PATCH 3/4] cgroup: make hierarchy_id use cyclic idr Tejun Heo
2013-04-14 18:36 ` [PATCH 4/4] cgroup: implement task_cgroup_path_from_hierarchy() Tejun Heo
2013-04-14 19:16 ` Greg KH
2013-04-15 3:43 ` Li Zefan
2013-04-15 3:46 ` Tejun Heo
2013-04-15 3:48 ` Tejun Heo
2013-04-15 3:49 ` Li Zefan
2013-04-15 3:57 ` Tejun Heo
2013-04-15 3:50 ` [PATCH UPDATED " Tejun Heo
2013-04-15 3:22 ` [PATCHSET] " Tejun Heo
2013-04-15 3:43 ` Li Zefan [this message]
2013-05-14 18:45 ` Tejun Heo
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=516B777B.9050704@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=daniel@zonque.org \
--cc=greg@kroah.com \
--cc=kay@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--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