linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Paul Menage <menage@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pavel Emelianov <xemul@openvz.org>,
	Hugh Dickins <hugh@veritas.com>,
	Sudhir Kumar <skumar@linux.vnet.ibm.com>,
	YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
	linux-kernel@vger.kernel.org, taka@valinux.co.jp,
	linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] Add cgroup support for enabling controllers at boot time
Date: Fri, 07 Mar 2008 13:56:32 +0900	[thread overview]
Message-ID: <47D0CB00.1040303@cn.fujitsu.com> (raw)
In-Reply-To: <47D0C67E.4080009@linux.vnet.ibm.com>

Balbir Singh wrote:
> Li Zefan wrote:
>> Balbir Singh wrote:
>>> From: Paul Menage <menage@google.com>
>>>
>>> The effects of cgroup_disable=foo are:
>>>
>>> - foo doesn't show up in /proc/cgroups
>>> - foo isn't auto-mounted if you mount all cgroups in a single hierarchy
>>> - foo isn't visible as an individually mountable subsystem
>>>
>>> As a result there will only ever be one call to foo->create(), at init
>>> time; all processes will stay in this group, and the group will never
>>> be mounted on a visible hierarchy. Any additional effects (e.g. not
>>> allocating metadata) are up to the foo subsystem.
>>>
>>> This doesn't handle early_init subsystems (their "disabled" bit isn't
>>> set be, but it could easily be extended to do so if any of the early_init
>>> systems wanted it - I think it would just involve some nastier parameter
>>> processing since it would occur before the command-line argument parser
>>> had been run.
>>>
>>> [Balbir added Documentation/kernel-parameters updates]
>>>
>>> Signed-off-by: Paul Menage <menage@google.com>
>>> Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
>>> ---
>>>
>>>  Documentation/kernel-parameters.txt |    4 ++++
>>>  include/linux/cgroup.h              |    1 +
>>>  kernel/cgroup.c                     |   27 +++++++++++++++++++++++++--
>>>  3 files changed, 30 insertions(+), 2 deletions(-)
>>>
>>> diff -puN include/linux/cgroup.h~cgroup_disable include/linux/cgroup.h
>>> --- linux-2.6.25-rc4/include/linux/cgroup.h~cgroup_disable   
>>> 2008-03-06 12:19:38.000000000 +0530
>>> +++ linux-2.6.25-rc4-balbir/include/linux/cgroup.h    2008-03-06
>>> 12:19:38.000000000 +0530
>>> @@ -256,6 +256,7 @@ struct cgroup_subsys {
>>>      void (*bind)(struct cgroup_subsys *ss, struct cgroup *root);
>>>      int subsys_id;
>>>      int active;
>>> +    int disabled;
>>>      int early_init;
>>>  #define MAX_CGROUP_TYPE_NAMELEN 32
>>>      const char *name;
>>> diff -puN kernel/cgroup.c~cgroup_disable kernel/cgroup.c
>>> --- linux-2.6.25-rc4/kernel/cgroup.c~cgroup_disable    2008-03-06
>>> 12:19:38.000000000 +0530
>>> +++ linux-2.6.25-rc4-balbir/kernel/cgroup.c    2008-03-06
>>> 12:19:38.000000000 +0530
>>> @@ -782,7 +782,14 @@ static int parse_cgroupfs_options(char *
>>>          if (!*token)
>>>              return -EINVAL;
>>>          if (!strcmp(token, "all")) {
>>> -            opts->subsys_bits = (1 << CGROUP_SUBSYS_COUNT) - 1;
>>> +            /* Add all non-disabled subsystems */
>>> +            int i;
>>> +            opts->subsys_bits = 0;
>>> +            for (i = 0; i < CGROUP_SUBSYS_COUNT; i++) {
>>> +                struct cgroup_subsys *ss = subsys[i];
>>> +                if (!ss->disabled)
>>> +                    opts->subsys_bits |= 1ul << i;
>>> +            }
>>>          } else if (!strcmp(token, "noprefix")) {
>>>              set_bit(ROOT_NOPREFIX, &opts->flags);
>>>          } else if (!strncmp(token, "release_agent=", 14)) {
>>> @@ -800,7 +807,8 @@ static int parse_cgroupfs_options(char *
>>>              for (i = 0; i < CGROUP_SUBSYS_COUNT; i++) {
>>>                  ss = subsys[i];
>>>                  if (!strcmp(token, ss->name)) {
>>> -                    set_bit(i, &opts->subsys_bits);
>>> +                    if (!ss->disabled)
>>> +                        set_bit(i, &opts->subsys_bits);
>>>                      break;
>>>                  }
>>>              }
>>> @@ -2604,6 +2612,8 @@ static int proc_cgroupstats_show(struct     
>>> mutex_lock(&cgroup_mutex);
>>>      for (i = 0; i < CGROUP_SUBSYS_COUNT; i++) {
>>>          struct cgroup_subsys *ss = subsys[i];
>>> +        if (ss->disabled)
>>> +            continue;
>>>          seq_printf(m, "%s\t%lu\t%d\n",
>>>                 ss->name, ss->root->subsys_bits,
>>>                 ss->root->number_of_cgroups);
>>> @@ -3010,3 +3020,16 @@ static void cgroup_release_agent(struct     
>>> spin_unlock(&release_list_lock);
>>>      mutex_unlock(&cgroup_mutex);
>>>  }
>>> +
>>> +static int __init cgroup_disable(char *str)
>>> +{
>>> +    int i;
>>> +    for (i = 0; i < CGROUP_SUBSYS_COUNT; i++) {
>>> +        struct cgroup_subsys *ss = subsys[i];
>>> +        if (!strcmp(str, ss->name)) {
>>> +            ss->disabled = 1;
>>> +            break;
>>> +        }
>>> +    }
>>> +}
>>> +__setup("cgroup_disable=", cgroup_disable);
>>> diff -puN Documentation/kernel-parameters.txt~cgroup_disable
>>> Documentation/kernel-parameters.txt
>>> ---
>>> linux-2.6.25-rc4/Documentation/kernel-parameters.txt~cgroup_disable   
>>> 2008-03-06 17:57:32.000000000 +0530
>>> +++ linux-2.6.25-rc4-balbir/Documentation/kernel-parameters.txt   
>>> 2008-03-06 18:00:32.000000000 +0530
>>> @@ -383,6 +383,10 @@ and is between 256 and 4096 characters.     
>>> ccw_timeout_log [S390]
>>>              See Documentation/s390/CommonIO for details.
>>>  
>>> +    cgroup_disable= [KNL] Enable disable a particular controller
>>> +            Format: {name of the controller}
>>> +            See /proc/cgroups for a list of compiled controllers
>>> +
>> The changelog of this patch:
>> - foo doesn't show up in /proc/cgroups
>>
>> So a disabled subsystem won't show up in /proc/cgroups. In a previous
>> mail, I asked whether it will be useful to print out the disable bit
>> in /proc/cgroups, so we can distinguish a subsystem from disaled and
>> not-compiled.
> 
> Hi, Li,
> 
> That is a good idea, but can that come in later? We need to get the boot option
> in, so that users can decide at boot time whether they want the page_container
> overhead. I'll send out another set of patches to add that feature or work
> with Paul to see what he thinks about it.
> 

I'm not requiring this to be done in this patch. :)

But my exact meaning here is this sentence is confusing:

	See /proc/cgroups for a list of compiled controllers

It seems it is telling people that /proc/cgroups shows not only enabled
but also disabled cgroup subsystems.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2008-03-07  4:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 18:59 [PATCH] Add cgroup support for enabling controllers at boot time Balbir Singh
2008-03-06 19:00 ` [PATCH] Make memory resource control aware of boot options Balbir Singh
2008-03-06 19:10 ` [PATCH] Add cgroup support for enabling controllers at boot time David Rientjes
2008-03-07  4:41   ` Balbir Singh
2008-03-07  4:58     ` KAMEZAWA Hiroyuki
2008-03-07  5:15       ` David Rientjes
2008-03-07  5:14     ` David Rientjes
2008-03-07  8:40       ` Paul Menage
2008-03-07  8:56         ` David Rientjes
2008-03-07  9:01           ` Paul Menage
2008-03-06 19:11 ` Randy Dunlap
2008-03-07  0:05   ` Li Zefan
2008-03-07  4:37     ` Balbir Singh
2008-03-07  0:13 ` Li Zefan
2008-03-07  4:37   ` Balbir Singh
2008-03-07  4:56     ` 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=47D0CB00.1040303@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=menage@google.com \
    --cc=rientjes@google.com \
    --cc=skumar@linux.vnet.ibm.com \
    --cc=taka@valinux.co.jp \
    --cc=xemul@openvz.org \
    --cc=yamamoto@valinux.co.jp \
    /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;
as well as URLs for NNTP newsgroup(s).