From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Control Groups Roadmap ideas
Date: Wed, 09 Apr 2008 10:28:15 +0800 [thread overview]
Message-ID: <47FC29BF.20701@cn.fujitsu.com> (raw)
In-Reply-To: <6599ad830804081414x7be75d2fte5b500a7f81df40c@mail.gmail.com>
Paul Menage wrote:
> 3) Subsystem dependencies
> -----
>
> This would be a fairly simple change, essentially allowing one
> subsystem to require that it only be mounted on a hierarchy when some
> other subsystem was also present. The implementation would probably be
> a callback that allows a subsystem to confirm whether it's prepared to
> be included in a proposed hierarchy containing a specified subsystem
> bitmask; it would be able to prevent the hierarchy from being created
> by giving an error return. An example of a use for this would be a
> swap subsystem that is mostly independent of the memory controller,
> but uses the page-ownership tracking of the memory controller to
> determine which cgroup to charge swap pages to. Hence it would require
> that it only be mounted on a hierarchy that also included a memory
> controller. The memory controller would make no such requirement by
> itself, so could be used on its own without the swap controller.
>
Sounds good, and I wrote a prototype in a quick:
diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index a6a6035..091bc21 100644
--- a/include/linux/cgroup.h
+++ b/include/linux/cgroup.h
@@ -254,6 +254,7 @@ struct cgroup_subsys {
struct cgroup *cgrp);
void (*post_clone)(struct cgroup_subsys *ss, struct cgroup *cgrp);
void (*bind)(struct cgroup_subsys *ss, struct cgroup *root);
+ int (*can_mount)(struct cgroup_subsys *ss, unsigned long subsys_bits);
int subsys_id;
int active;
int disabled;
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 62f1a52..3d43ff2 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@ -824,6 +824,25 @@ static int parse_cgroupfs_options(char *data,
return 0;
}
+static int check_mount(unsigned long subsys_bits)
+{
+ int i;
+ int ret;
+ struct cgroup_subsys *ss;
+
+ for (i = 0; i < CGROUP_SUBSYS_COUNT; i++) {
+ ss = subsys[i];
+
+ if (test_bit(i, &subsys_bits) && ss->can_mount) {
+ ret = ss->can_mount(ss, subsys_bits);
+ if (ret)
+ return ret;
+ }
+ }
+
+ return 0;
+}
+
static int cgroup_remount(struct super_block *sb, int *flags, char *data)
{
int ret = 0;
@@ -839,6 +858,10 @@ static int cgroup_remount(struct super_block *sb, int *flags, char *data)
if (ret)
goto out_unlock;
+ ret = check_mount(opts.subsys_bits);
+ if (ret)
+ goto out_unlock;
+
/* Don't allow flags to change at remount */
if (opts.flags != root->flags) {
ret = -EINVAL;
@@ -959,6 +982,13 @@ static int cgroup_get_sb(struct file_system_type *fs_type,
return ret;
}
+ ret = check_mount(opts.subsys_bits);
+ if (ret) {
+ if (opts.release_agent)
+ kfree(opts.release_agent);
+ return ret;
+ }
+
root = kzalloc(sizeof(*root), GFP_KERNEL);
if (!root) {
if (opts.release_agent)
-------
for the example about swap controller and memory controller:
static int swap_cgroup_can_mount(struct cgroup_subsys *ss,
unsigned long subsys_bits)
{
if (!test_bit(mem_cgroup_subsys_id, &subsys_bits))
return -EINVAL;
return 0;
}
'mem_cgroup_subsys_id' is a member of enum cgroup_subsys_id defined in cgroup.h
next prev parent reply other threads:[~2008-04-09 2:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 21:14 [RFC] Control Groups Roadmap ideas Paul Menage
2008-04-09 2:28 ` Li Zefan [this message]
[not found] ` <47FC29BF.20701-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-04-10 20:10 ` Paul Menage
2008-04-10 20:10 ` Paul Menage
2008-04-11 14:48 ` Serge E. Hallyn
[not found] ` <20080411144836.GA6468-6s5zFf/epYJZE39wxRU1Vbcc1pwJh6gGAChmaU/rkALQT0dZR+AlfA@public.gmane.org>
2008-04-12 5:10 ` Balbir Singh
2008-04-12 5:10 ` Balbir Singh
[not found] ` <661de9470804112210h49ef1371p2c3102ffdf2791f2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-13 16:11 ` Serge E. Hallyn
2008-04-13 16:11 ` Serge E. Hallyn
[not found] ` <20080413161127.GB7010-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-04-14 14:31 ` Balbir Singh
2008-04-14 14:31 ` Balbir Singh
2008-04-14 5:24 ` Paul Menage
2008-04-14 5:24 ` Paul Menage
2008-04-14 14:11 ` Serge E. Hallyn
[not found] ` <20080414141119.GA11019-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-04-14 15:03 ` Paul Menage
2008-04-14 15:03 ` Paul Menage
[not found] ` <6599ad830804132224h4b958891i101c6e068ea15f55-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-14 14:11 ` Serge E. Hallyn
[not found] ` <6599ad830804081414x7be75d2fte5b500a7f81df40c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-09 2:28 ` Li Zefan
2008-04-11 14:48 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2008-04-08 21:14 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=47FC29BF.20701@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.