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: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	balbir@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, containers@lists.linux-foundation.org
Subject: Re: [PATCH 1/9] [RFC] Support named cgroups hierarchies
Date: Fri, 03 Jul 2009 09:51:53 +0800	[thread overview]
Message-ID: <4A4D6439.8030302@cn.fujitsu.com> (raw)
In-Reply-To: <6599ad830907011949h13598e36m45b85ae76900b90a@mail.gmail.com>

>>>  /*
>>>   * A cgroupfs_root represents the root of a cgroup hierarchy,
>>>   * and may be associated with a superblock to form an active
>>> @@ -93,6 +95,9 @@ struct cgroupfs_root {
>>>
>>>       /* The path to use for release notifications. */
>>>       char release_agent_path[PATH_MAX];
>>> +
>>> +     /* The name for this hierarchy - may be empty */
>>> +     char name[MAX_CGROUP_ROOT_NAMELEN];
>>>  };
>>>
>> If you don't want to make cgroupfs_root bigger,
>>
>>        cgroupfs_root {
>>                ......
>>                /* this must be the bottom of struct */
>>                char name[0];
>>        }
>>
>> Is a choice.
> 
> I'd rather avoid something like that since I think it's less readable
> - I'd probably just make the name into a pointer in that case.
> 

Whichever choice we make, the length should be limited I think.

>> BTW, reading a patch, any kind of charactors are allowed ?
> 
> Yes, other than \000 of course. I guess maybe I should use
> seq_escape() to print the name to avoid confusion in the event that
> people put whitespace in there, or else just ban whitespace (or maybe
> all non-alphanumeric chars).
> 

I don't think we need to care about this.

mount -t cgroup -o debug xxx /mnt

"xxx" can be any chars.



  reply	other threads:[~2009-07-03  1:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  2:10 [PATCH 0/9] [RFC] CGroup Hierarchy Extensions Paul Menage
2009-07-02  2:10 ` [PATCH 1/9] [RFC] Support named cgroups hierarchies Paul Menage
2009-07-02  2:28   ` KAMEZAWA Hiroyuki
2009-07-02  2:49     ` Paul Menage
2009-07-03  1:51       ` Li Zefan [this message]
2009-07-02  8:09   ` Louis Rilling
2009-07-02  8:19     ` Paul Menage
2009-07-02  8:24       ` Louis Rilling
2009-07-03  2:32   ` Li Zefan
2009-07-13 23:39     ` Paul Menage
2009-07-02  2:11 ` [PATCH 2/9] [RFC]Move the cgroup debug subsys into cgroup.c to access internal state Paul Menage
2009-07-02  2:11 ` [PATCH 3/9] [RFC] Add a back-pointer from struct cg_cgroup_link to struct cgroup Paul Menage
2009-07-03  7:07   ` Li Zefan
2009-07-21 23:48     ` Paul Menage
2009-07-02  2:11 ` [PATCH 4/9] [RFC] Allow cgroup hierarchies to be created with no bound subsystems Paul Menage
2009-07-03  7:57   ` Li Zefan
2009-07-21 23:31     ` Paul Menage
2009-07-02  2:11 ` [PATCH 5/9] [RFC] Remove cgroup_subsys.root pointer Paul Menage
2009-07-02  9:04   ` Louis Rilling
2009-07-02  9:32     ` Paul Menage
2009-07-02  2:11 ` [PATCH 6/9] [RFC] Remove the cgroup_subsys.bind callback Paul Menage
2009-07-02  2:11 ` [PATCH 7/9] [RFC] Support multiply-bindable cgroup subsystems Paul Menage
2009-07-02  2:45   ` KAMEZAWA Hiroyuki
2009-07-02  2:52     ` Paul Menage
2009-07-02  3:16       ` KAMEZAWA Hiroyuki
2009-07-02  5:04         ` Paul Menage
2009-07-03  8:36   ` Li Zefan
2009-07-02  2:11 ` [PATCH 8/9] [RFC] Example multi-bindable subsystem: a per-cgroup notes field Paul Menage
2009-07-02  2:48   ` KAMEZAWA Hiroyuki
2009-07-02  2:56     ` Paul Menage
2009-07-02  3:17       ` KAMEZAWA Hiroyuki
2009-07-02  7:22       ` Paul Menage
2009-07-03  8:58   ` Li Zefan
2009-07-14  0:49     ` Paul Menage
2009-07-02  2:11 ` [PATCH 9/9] [RFC] Example multi-bindable subsystem: a max-depth controller 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=4A4D6439.8030302@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --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