public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Menage <menage@google.com>
To: containers@lists.linux-foundation.org
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [RFC][PATCH] CGroups: Include hierarchy ids in /proc/<pid>/cgroup
Date: Tue, 08 Apr 2008 17:05:51 -0700	[thread overview]
Message-ID: <47FC085F.2070709@google.com> (raw)

[ The RFC associated with this patch is whether there's a better way to export such information in a way that's simultaneously extensible, human-readable and machine-parsable ]

CGroups: Include hierarchy ids in /proc/<pid>/cgroup

This patch extends the /proc/<pid>/cgroup file to include the
appropriate hierarchy ID on each line. Currently this ID isn't really
needed since a hierarchy can be completely identified by the set of
subsystems bound to it, but this is likely to change in the near
future in order to support stateless subsystems and merging/rebinding
of subsystems. Getting this change into 2.6.25 reduces the need for
an API change later.

Signed-off-by: Paul Menage <menage@google.com>

---
 kernel/cgroup.c |    1 +
 1 file changed, 1 insertion(+)

Index: cgroup-2.6.25-rc8-mm1/kernel/cgroup.c
===================================================================
--- cgroup-2.6.25-rc8-mm1.orig/kernel/cgroup.c
+++ cgroup-2.6.25-rc8-mm1/kernel/cgroup.c
@@ -2613,6 +2613,7 @@ static int proc_cgroup_show(struct seq_f
 		/* Skip this hierarchy if it has no active subsystems */
 		if (!root->actual_subsys_bits)
 			continue;
+		seq_printf(m, "%lu:", root->subsys_bits);
 		for_each_subsys(root, ss)
 			seq_printf(m, "%s%s", count++ ? "," : "", ss->name);
 		seq_putc(m, ':');

                 reply	other threads:[~2008-04-09  0:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47FC085F.2070709@google.com \
    --to=menage@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.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