[PATCH] add new cgroup list to CC notice

[PATCH] add new cgroup list to CC notice

[KAMEZAWA Hiroyuki]

As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
James. This list is for discussing general cgroup design and patches
including all subsystems and for getting more attentions to cgroups/namespaces
related issues by developpers.

Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
---
 MAINTAINERS |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index ab77670..2d6b4ba 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1927,6 +1927,7 @@ CONTROL GROUPS (CGROUPS)
 M:	Paul Menage <paul-inf54ven1CmVyaH7bEyXVA@public.gmane.org>
 M:	Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
 L:	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
+L:	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
 S:	Maintained
 F:	include/linux/cgroup*
 F:	kernel/cgroup*
@@ -4294,6 +4295,7 @@ MEMORY RESOURCE CONTROLLER
 M:	Balbir Singh <bsingharora-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
 M:	Daisuke Nishimura <nishimura-YQH0OdQVrdy45+QrQBaojngSJqDPrsil@public.gmane.org>
 M:	KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
+L:	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
 L:	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org
 S:	Maintained
 F:	mm/memcontrol.c
-- 
1.7.4.1

[PATCH] add new cgroup list to CC notice

[KAMEZAWA Hiroyuki]

As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
James. This list is for discussing general cgroup design and patches
including all subsystems and for getting more attentions to cgroups/namespaces
related issues by developpers.

Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
 MAINTAINERS |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index ab77670..2d6b4ba 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1927,6 +1927,7 @@ CONTROL GROUPS (CGROUPS)
 M:	Paul Menage <paul@paulmenage.org>
 M:	Li Zefan <lizf@cn.fujitsu.com>
 L:	containers@lists.linux-foundation.org
+L:	cgroups@vger.kernel.org
 S:	Maintained
 F:	include/linux/cgroup*
 F:	kernel/cgroup*
@@ -4294,6 +4295,7 @@ MEMORY RESOURCE CONTROLLER
 M:	Balbir Singh <bsingharora@gmail.com>
 M:	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
 M:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
+L:	cgroups@vger.kernel.org
 L:	linux-mm@kvack.org
 S:	Maintained
 F:	mm/memcontrol.c
-- 
1.7.4.1

Re: [PATCH] add new cgroup list to CC notice

[Daniel Lezcano]

On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> James. This list is for discussing general cgroup design and patches
> including all subsystems and for getting more attentions to cgroups/namespaces
> related issues by developpers.
>
> Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
> ---

I don't see the point to unilaterally change the mailing list to 
vger.kernel.org as the discussions will be  the same as the actual 
mailing list containers@. May be there is a good reason to do that but I 
don't see it, can someone enlight me please ?

Re: [PATCH] add new cgroup list to CC notice

[Daniel Lezcano]

On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> James. This list is for discussing general cgroup design and patches
> including all subsystems and for getting more attentions to cgroups/namespaces
> related issues by developpers.
>
> Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com>
> ---

I don't see the point to unilaterally change the mailing list to 
vger.kernel.org as the discussions will be  the same as the actual 
mailing list containers@. May be there is a good reason to do that but I 
don't see it, can someone enlight me please ?

Re: [PATCH] add new cgroup list to CC notice

[KAMEZAWA Hiroyuki]

On Fri, 04 Nov 2011 03:09:31 +0100
Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org> wrote:

> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> > As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> > James. This list is for discussing general cgroup design and patches
> > including all subsystems and for getting more attentions to cgroups/namespaces
> > related issues by developpers.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
> > ---
> 
> I don't see the point to unilaterally change the mailing list to 
> vger.kernel.org as the discussions will be  the same as the actual 
> mailing list containers@. May be there is a good reason to do that but I 
> don't see it, can someone enlight me please ?
> 
I know containers@ and subscribing it.

Maybe this article is good.
http://lwn.net/Articles/464288/

I think there are cgroups not-for-container but total view/interaction
are required. someones may use cgroup just as resource controller (as libvirt,
systemd) and not be intereted in container itself.

I personally think cgroups@ is a straightforward name to kernel developpers. 

Thanks,
-Kame

Re: [PATCH] add new cgroup list to CC notice

[KAMEZAWA Hiroyuki]

On Fri, 04 Nov 2011 03:09:31 +0100
Daniel Lezcano <daniel.lezcano@free.fr> wrote:

> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> > As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> > James. This list is for discussing general cgroup design and patches
> > including all subsystems and for getting more attentions to cgroups/namespaces
> > related issues by developpers.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> 
> I don't see the point to unilaterally change the mailing list to 
> vger.kernel.org as the discussions will be  the same as the actual 
> mailing list containers@. May be there is a good reason to do that but I 
> don't see it, can someone enlight me please ?
> 
I know containers@ and subscribing it.

Maybe this article is good.
http://lwn.net/Articles/464288/

I think there are cgroups not-for-container but total view/interaction
are required. someones may use cgroup just as resource controller (as libvirt,
systemd) and not be intereted in container itself.

I personally think cgroups@ is a straightforward name to kernel developpers. 

Thanks,
-Kame

Re: [PATCH] add new cgroup list to CC notice

[James Bottomley]

On Fri, 2011-11-04 at 03:09 +0100, Daniel Lezcano wrote:
> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> > As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> > James. This list is for discussing general cgroup design and patches
> > including all subsystems and for getting more attentions to cgroups/namespaces
> > related issues by developpers.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
> > ---
> 
> I don't see the point to unilaterally change the mailing list to 
> vger.kernel.org as the discussions will be  the same as the actual 
> mailing list containers@.

It's not a unilateral list change.  We will still have containers@lf.

The problem is that not all cgroup related stuff goes over it ...
particularly the currently active controller discussions tend not to be
cc'd there.  With systemd (and things like the I/O controllers for
xen/kvm), cgroups is seen as being wider than containers.

The desire was for a single list where someone could go to get an
overall view of what's going on in cgroups ... particularly if you're a
confused subsystem maintainer who just had a request to put a controller
in your subsystem ...

James

>  May be there is a good reason to do that but I 
> don't see it, can someone enlight me please ?
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] add new cgroup list to CC notice

[James Bottomley]

On Fri, 2011-11-04 at 03:09 +0100, Daniel Lezcano wrote:
> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> > As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> > James. This list is for discussing general cgroup design and patches
> > including all subsystems and for getting more attentions to cgroups/namespaces
> > related issues by developpers.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> 
> I don't see the point to unilaterally change the mailing list to 
> vger.kernel.org as the discussions will be  the same as the actual 
> mailing list containers@.

It's not a unilateral list change.  We will still have containers@lf.

The problem is that not all cgroup related stuff goes over it ...
particularly the currently active controller discussions tend not to be
cc'd there.  With systemd (and things like the I/O controllers for
xen/kvm), cgroups is seen as being wider than containers.

The desire was for a single list where someone could go to get an
overall view of what's going on in cgroups ... particularly if you're a
confused subsystem maintainer who just had a request to put a controller
in your subsystem ...

James

>  May be there is a good reason to do that but I 
> don't see it, can someone enlight me please ?
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] add new cgroup list to CC notice

[Daniel Lezcano]

On 11/04/2011 05:50 AM, James Bottomley wrote:
> On Fri, 2011-11-04 at 03:09 +0100, Daniel Lezcano wrote:
>> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
>>> As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
>>> James. This list is for discussing general cgroup design and patches
>>> including all subsystems and for getting more attentions to cgroups/namespaces
>>> related issues by developpers.
>>>
>>> Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com>
>>> ---
>> I don't see the point to unilaterally change the mailing list to
>> vger.kernel.org as the discussions will be  the same as the actual
>> mailing list containers@.
> It's not a unilateral list change.  We will still have containers@lf.
>
> The problem is that not all cgroup related stuff goes over it ...
> particularly the currently active controller discussions tend not to be
> cc'd there.  With systemd (and things like the I/O controllers for
> xen/kvm), cgroups is seen as being wider than containers.
>
> The desire was for a single list where someone could go to get an
> overall view of what's going on in cgroups ... particularly if you're a
> confused subsystem maintainer who just had a request to put a controller
> in your subsystem ...

Ok, thanks for the clarification. May I suggest to create also a 
namespace@ mailing list ?

Re: [PATCH] add new cgroup list to CC notice

[Daniel Lezcano]

On 11/04/2011 05:50 AM, James Bottomley wrote:
> On Fri, 2011-11-04 at 03:09 +0100, Daniel Lezcano wrote:
>> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
>>> As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
>>> James. This list is for discussing general cgroup design and patches
>>> including all subsystems and for getting more attentions to cgroups/namespaces
>>> related issues by developpers.
>>>
>>> Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
>>> ---
>> I don't see the point to unilaterally change the mailing list to
>> vger.kernel.org as the discussions will be  the same as the actual
>> mailing list containers@.
> It's not a unilateral list change.  We will still have containers@lf.
>
> The problem is that not all cgroup related stuff goes over it ...
> particularly the currently active controller discussions tend not to be
> cc'd there.  With systemd (and things like the I/O controllers for
> xen/kvm), cgroups is seen as being wider than containers.
>
> The desire was for a single list where someone could go to get an
> overall view of what's going on in cgroups ... particularly if you're a
> confused subsystem maintainer who just had a request to put a controller
> in your subsystem ...

Ok, thanks for the clarification. May I suggest to create also a 
namespace@ mailing list ?