From: Li Zefan <lizf@cn.fujitsu.com>
To: bblum@andrew.cmu.edu
Cc: linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
Paul Menage <menage@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/3] cgroups: support for module-loadable subsystems
Date: Tue, 03 Nov 2009 10:03:42 +0800 [thread overview]
Message-ID: <4AEF8F7E.1000007@cn.fujitsu.com> (raw)
In-Reply-To: <20091102212825.GA13692@andrew.cmu.edu>
Ben Blum wrote:
> This patch series implements simple support for building and loading
> subsystems as modules, both within and outside the kernel source tree.
> Module unloading is as yet unimplemented - it will require more advanced
> reference counting in the mount/unmount code, and I plan to work on this
> soon.
>
I doubt the value of module-loadable subsystems. A cgroup subsystem
is usually a kernel resource controller, and normally it needs to
add some hooks in some in-kernel structures and functions, which
makes it impossible to be a module.
In fact, net_cls is the only subsystem that can be a module, and
make it a module doesn't seem to have real benefit?
> Patch #1 sets up the subsys[] array so its contents can be dynamic as
> modules appear and (eventually) disappear. I introduce an rwsem called
> subsys_mutex to protect against concurrent loads/unloads/reads, and
> modify iterations over the array to handle when subsystems are absent.
>
> Patch #2 implements an interface for modules to load subsystems, called
> cgroup_load_subsys, similar to cgroup_init_subsys, and adds a module
> pointer in struct cgroup_subsys.
>
> Patch #3 modifies the net_cls subsystem, which already had some module
> declarations, to be configurable as a module, which also serves as a
> simple proof-of-concept.
>
> -- bblum
>
next prev parent reply other threads:[~2009-11-03 2:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 21:28 [RFC][PATCH 0/3] cgroups: support for module-loadable subsystems Ben Blum
2009-11-02 21:28 ` Ben Blum
2009-11-03 2:03 ` Li Zefan [this message]
2009-11-03 2:11 ` Paul Menage
2009-11-03 2:42 ` Li Zefan
[not found] ` <6599ad830911021811n7ccf7a70y6939ac581381c22f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-03 2:42 ` Li Zefan
[not found] ` <4AEF8F7E.1000007-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-11-03 2:11 ` Paul Menage
[not found] ` <20091102212825.GA13692-OM76b2Iv3yLQjUSlxSEPGw@public.gmane.org>
2009-11-02 21:29 ` [RFC][PATCH 1/3] cgroups: revamp subsys array Ben Blum
2009-11-02 21:29 ` Ben Blum
2009-11-02 21:30 ` [RFC][PATCH 2/3] cgroups: subsystem module interface Ben Blum
2009-11-02 21:30 ` Ben Blum
[not found] ` <20091102213022.GC13692-OM76b2Iv3yLQjUSlxSEPGw@public.gmane.org>
2009-11-04 20:30 ` Ben Blum
2009-11-04 20:30 ` Ben Blum
[not found] ` <20091104203024.GA14471-OM76b2Iv3yLQjUSlxSEPGw@public.gmane.org>
2009-11-04 21:18 ` Paul Menage
2009-11-04 21:18 ` Paul Menage
2009-11-02 21:31 ` [RFC][PATCH 3/3] cgroups: net_cls subsys as module Ben Blum
2009-11-02 21:31 ` Ben Blum
[not found] ` <20091102213103.GD13692-OM76b2Iv3yLQjUSlxSEPGw@public.gmane.org>
2009-11-02 21:46 ` Randy Dunlap
2009-11-02 21:46 ` Randy Dunlap
2009-11-03 2:03 ` [RFC][PATCH 0/3] cgroups: support for module-loadable subsystems Li Zefan
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=4AEF8F7E.1000007@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=bblum@andrew.cmu.edu \
--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.