From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: akpm@linux-foundation.org, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] Add a back-pointer from struct cg_cgroup_link to struct cgroup
Date: Thu, 23 Jul 2009 14:44:41 +0800 [thread overview]
Message-ID: <4A6806D9.8020004@cn.fujitsu.com> (raw)
In-Reply-To: <20090722195040.7481.44939.stgit@menage.mtv.corp.google.com>
Paul Menage wrote:
> Add a back-pointer from struct cg_cgroup_link to struct cgroup
>
> Currently the cgroups code makes the assumption that the subsystem
> pointers in a struct css_set uniquely identify the hierarchy->cgroup
> mappings associated with the css_set; and there's no way to directly
> identify the associated set of cgroups other than by indirecting
> through the appropriate subsystem state pointers.
>
> This patch removes the need for that assumption by adding a
> back-pointer from struct cg_cgroup_link object to its associated
> cgroup; this allows the set of cgroups to be determined by traversing
> the cg_links list in the struct css_set.
>
> Signed-off-by: Paul Menage <menage@google.com>
>
Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>
...
> +#define MAX_TASKS_SHOWN_PER_CSS 25
> +static int cgroup_css_links_read(struct cgroup *cont,
> + struct cftype *cft,
> + struct seq_file *seq)
> +{
> + struct cg_cgroup_link *link;
> +
I think we need to cgroup_enable_task_cg_lists():
if (!use_task_css_set_links)
cgroup_enable_task_cg_lists();
Otherwise we'll see no tasks when reading this debug file
if use_task_css_set_links == 0.
> + read_lock(&css_set_lock);
> + list_for_each_entry(link, &cont->css_sets, cgrp_link_list) {
> + struct css_set *cg = link->cg;
> + struct task_struct *task;
> + int count = 0;
> + seq_printf(seq, "css_set %p\n", cg);
> + list_for_each_entry(task, &cg->tasks, cg_list) {
> + if (count++ > MAX_TASKS_SHOWN_PER_CSS) {
> + seq_puts(seq, " ...\n");
> + break;
> + } else {
> + seq_printf(seq, " task %d\n",
> + task_pid_vnr(task));
> + }
> + }
> + }
> + read_unlock(&css_set_lock);
> + return 0;
> +}
next prev parent reply other threads:[~2009-07-23 6:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 19:50 [PATCH 0/4] CGroup: Support for named and empty hierarchies Paul Menage
2009-07-22 19:50 ` [PATCH 1/4] Support named cgroups hierarchies Paul Menage
2009-07-23 6:20 ` Li Zefan
2009-07-23 6:27 ` Paul Menage
2009-07-23 6:50 ` Li Zefan
2009-07-28 23:17 ` Paul Menage
2009-07-23 6:47 ` KAMEZAWA Hiroyuki
2009-07-22 19:50 ` [PATCH 2/4] Move the cgroup debug subsys into cgroup.c to access internal state Paul Menage
2009-07-23 6:21 ` Li Zefan
2009-07-23 6:51 ` KAMEZAWA Hiroyuki
2009-07-22 19:50 ` [PATCH 3/4] Add a back-pointer from struct cg_cgroup_link to struct cgroup Paul Menage
2009-07-23 6:44 ` Li Zefan [this message]
2009-07-23 14:31 ` Paul Menage
2009-07-22 19:50 ` [PATCH 4/4] Allow cgroup hierarchies to be created with no bound subsystems Paul Menage
2009-07-23 8:19 ` KAMEZAWA Hiroyuki
2009-07-23 8:32 ` Li Zefan
2009-07-24 5:21 ` Li Zefan
2009-07-23 5:13 ` [PATCH 0/4] CGroup: Support for named and empty hierarchies KAMEZAWA Hiroyuki
2009-07-23 5:37 ` Paul Menage
2009-07-23 5:45 ` KAMEZAWA Hiroyuki
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 23:26 Paul Menage
2009-07-28 23:26 ` [PATCH 3/4] Add a back-pointer from struct cg_cgroup_link to struct cgroup Paul Menage
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=4A6806D9.8020004@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
/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