LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Re: [PATCH] memcg: clarify use_hierarchy documentation
  2011-02-17  1:51 [PATCH] memcg: clarify use_hierarchy documentation Greg Thelen
@ 2011-02-17  1:49 ` KAMEZAWA Hiroyuki
  2011-02-17  8:17   ` Jiri Kosina
  0 siblings, 1 reply; 4+ messages in thread
From: KAMEZAWA Hiroyuki @ 2011-02-17  1:49 UTC (permalink / raw)
  To: Greg Thelen
  Cc: Andrew Morton, Randy Dunlap, Daisuke Nishimura, Jiri Kosina,
	linux-mm, linux-kernel

On Wed, 16 Feb 2011 17:51:23 -0800
Greg Thelen <gthelen@google.com> wrote:

> The memcg code does not allow changing memory.use_hierarchy if the
> parent cgroup has enabled use_hierarchy.  Update documentation to match
> the code.
> 
> Signed-off-by: Greg Thelen <gthelen@google.com>

Thank you,
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>

Because I tend to read linux-mm list 1st, I'm glad if you CC linux-mm in
the next time.

> ---
>  Documentation/cgroups/memory.txt |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> index 7781857..b6ed61c 100644
> --- a/Documentation/cgroups/memory.txt
> +++ b/Documentation/cgroups/memory.txt
> @@ -485,8 +485,9 @@ The feature can be disabled by
>  
>  # echo 0 > memory.use_hierarchy
>  
> -NOTE1: Enabling/disabling will fail if the cgroup already has other
> -       cgroups created below it.
> +NOTE1: Enabling/disabling will fail if either the cgroup already has other
> +       cgroups created below it, or if the parent cgroup has use_hierarchy
> +       enabled.
>  
>  NOTE2: When panic_on_oom is set to "2", the whole system will panic in
>         case of an OOM event in any cgroup.
> -- 
> 1.7.3.1
> 
> 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH] memcg: clarify use_hierarchy documentation
@ 2011-02-17  1:51 Greg Thelen
  2011-02-17  1:49 ` KAMEZAWA Hiroyuki
  0 siblings, 1 reply; 4+ messages in thread
From: Greg Thelen @ 2011-02-17  1:51 UTC (permalink / raw)
  To: Andrew Morton
  Cc: Randy Dunlap, KAMEZAWA Hiroyuki, Daisuke Nishimura, Jiri Kosina,
	linux-mm, linux-kernel, Greg Thelen

The memcg code does not allow changing memory.use_hierarchy if the
parent cgroup has enabled use_hierarchy.  Update documentation to match
the code.

Signed-off-by: Greg Thelen <gthelen@google.com>
---
 Documentation/cgroups/memory.txt |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index 7781857..b6ed61c 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -485,8 +485,9 @@ The feature can be disabled by
 
 # echo 0 > memory.use_hierarchy
 
-NOTE1: Enabling/disabling will fail if the cgroup already has other
-       cgroups created below it.
+NOTE1: Enabling/disabling will fail if either the cgroup already has other
+       cgroups created below it, or if the parent cgroup has use_hierarchy
+       enabled.
 
 NOTE2: When panic_on_oom is set to "2", the whole system will panic in
        case of an OOM event in any cgroup.
-- 
1.7.3.1


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] memcg: clarify use_hierarchy documentation
  2011-02-17  1:49 ` KAMEZAWA Hiroyuki
@ 2011-02-17  8:17   ` Jiri Kosina
  0 siblings, 0 replies; 4+ messages in thread
From: Jiri Kosina @ 2011-02-17  8:17 UTC (permalink / raw)
  To: KAMEZAWA Hiroyuki
  Cc: Greg Thelen, Andrew Morton, Randy Dunlap, Daisuke Nishimura,
	linux-mm, linux-kernel

On Thu, 17 Feb 2011, KAMEZAWA Hiroyuki wrote:

> On Wed, 16 Feb 2011 17:51:23 -0800
> Greg Thelen <gthelen@google.com> wrote:
> 
> > The memcg code does not allow changing memory.use_hierarchy if the
> > parent cgroup has enabled use_hierarchy.  Update documentation to match
> > the code.
> > 
> > Signed-off-by: Greg Thelen <gthelen@google.com>
> 
> Thank you,
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>

Applied, thanks.

> 
> Because I tend to read linux-mm list 1st, I'm glad if you CC linux-mm in
> the next time.
> 
> > ---
> >  Documentation/cgroups/memory.txt |    5 +++--
> >  1 files changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> > index 7781857..b6ed61c 100644
> > --- a/Documentation/cgroups/memory.txt
> > +++ b/Documentation/cgroups/memory.txt
> > @@ -485,8 +485,9 @@ The feature can be disabled by
> >  
> >  # echo 0 > memory.use_hierarchy
> >  
> > -NOTE1: Enabling/disabling will fail if the cgroup already has other
> > -       cgroups created below it.
> > +NOTE1: Enabling/disabling will fail if either the cgroup already has other
> > +       cgroups created below it, or if the parent cgroup has use_hierarchy
> > +       enabled.
> >  
> >  NOTE2: When panic_on_oom is set to "2", the whole system will panic in
> >         case of an OOM event in any cgroup.
> > -- 
> > 1.7.3.1
> > 
> > 
> 

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] memcg: clarify use_hierarchy documentation
       [not found] <201102170152.p1H1qKli008601@smtp-out.google.com>
@ 2011-02-17  1:57 ` Greg Thelen
  0 siblings, 0 replies; 4+ messages in thread
From: Greg Thelen @ 2011-02-17  1:57 UTC (permalink / raw)
  To: Andrew Morton
  Cc: Randy Dunlap, KAMEZAWA Hiroyuki, Daisuke Nishimura, Jiri Kosina,
	linux-mm, linux-kernel, Greg Thelen

(cc correct linux-mm address)

The memcg code does not allow changing memory.use_hierarchy if the
parent cgroup has enabled use_hierarchy.  Update documentation to match
the code.

Signed-off-by: Greg Thelen <gthelen@google.com>
---
 Documentation/cgroups/memory.txt |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index 7781857..b6ed61c 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -485,8 +485,9 @@ The feature can be disabled by
 
 # echo 0 > memory.use_hierarchy
 
-NOTE1: Enabling/disabling will fail if the cgroup already has other
-       cgroups created below it.
+NOTE1: Enabling/disabling will fail if either the cgroup already has other
+       cgroups created below it, or if the parent cgroup has use_hierarchy
+       enabled.
 
 NOTE2: When panic_on_oom is set to "2", the whole system will panic in
        case of an OOM event in any cgroup.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-02-17  8:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-17  1:51 [PATCH] memcg: clarify use_hierarchy documentation Greg Thelen
2011-02-17  1:49 ` KAMEZAWA Hiroyuki
2011-02-17  8:17   ` Jiri Kosina
     [not found] <201102170152.p1H1qKli008601@smtp-out.google.com>
2011-02-17  1:57 ` Greg Thelen

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).