public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: bblum@andrew.cmu.edu, linux-kernel@vger.kernel.org,
	Linux Containers <containers@lists.linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/3] cgroups: support for module-loadable subsystems
Date: Tue, 03 Nov 2009 10:42:02 +0800	[thread overview]
Message-ID: <4AEF987A.5090308@cn.fujitsu.com> (raw)
In-Reply-To: <6599ad830911021811n7ccf7a70y6939ac581381c22f@mail.gmail.com>

Paul Menage wrote:
> On Mon, Nov 2, 2009 at 6:03 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
>> 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.
> 
> Not true - as the classifier example shows, if there's already a
> framework that supports hooking loadable modules into some kernel
> system, a resource controller can be a module.
> 

True. Just reminds me a pure cfq-based io controller can be a
module too, though the io controller discussed in the mini summit
won't be a pure cfq-based one.

>> 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?
> 
> Wouldn't it be just as useful as any other module-loadable classifier,
> of which there are quite a few?
> 
> It's true that net_cls is currently the only subsystem that makes
> sense to use as a module, but its existence shows that the concept
> isn't too outlandish.
> 

Yes, sounds reasonable. 

      reply	other threads:[~2009-11-03  2:42 UTC|newest]

Thread overview: 10+ 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:29 ` [RFC][PATCH 1/3] cgroups: revamp subsys array Ben Blum
2009-11-02 21:30 ` [RFC][PATCH 2/3] cgroups: subsystem module interface Ben Blum
2009-11-04 20:30   ` Ben Blum
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:46   ` Randy Dunlap
2009-11-03  2:03 ` [RFC][PATCH 0/3] cgroups: support for module-loadable subsystems Li Zefan
2009-11-03  2:11   ` Paul Menage
2009-11-03  2:42     ` Li Zefan [this message]

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=4AEF987A.5090308@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox