From: Randy Dunlap <randy.dunlap@oracle.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memcg: update documentation v7
Date: Wed, 14 Apr 2010 11:11:46 -0700 [thread overview]
Message-ID: <20100414111146.c2907cd7.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100414102221.2c540a0d.kamezawa.hiroyu@jp.fujitsu.com>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> Documentation/cgroups/memory.txt | 289 ++++++++++++++++++++++++++-------------
> 1 file changed, 197 insertions(+), 92 deletions(-)
>
> Index: mmotm-temp/Documentation/cgroups/memory.txt
> ===================================================================
> --- mmotm-temp.orig/Documentation/cgroups/memory.txt
> +++ mmotm-temp/Documentation/cgroups/memory.txt
> @@ -1,18 +1,15 @@
> Memory Resource Controller
>
> NOTE: The Memory Resource Controller has been generically been referred
> -to as the memory controller in this document. Do not confuse memory controller
> -used here with the memory controller that is used in hardware.
> + to as the memory controller in this document. Do not confuse memory
> + controller used here with the memory controller that is used in hardware.
>
> -Salient features
> -
> -a. Enable control of Anonymous, Page Cache (mapped and unmapped) and
> - Swap Cache memory pages.
> -b. The infrastructure allows easy addition of other types of memory to control
> -c. Provides *zero overhead* for non memory controller users
> -d. Provides a double LRU: global memory pressure causes reclaim from the
> - global LRU; a cgroup on hitting a limit, reclaims from the per
> - cgroup LRU
> +(For editors)
> +In this document:
> + When we mention a cgroup (cgroupfs's directory) with memory controller,
> + we call it "memory cgroup". When you see git-log and source code, you'll
> + see patch's title and function names tend to use "memcg".
> + In this document, we avoid to use it.
we avoid using it.
>
> Benefits and Purpose of the memory controller
> @@ -501,27 +605,28 @@ It's applicable for root and non-root cg
>
> memory.oom_control file is for OOM notification and other controls.
>
> -Memory controler implements oom notifier using cgroup notification
> -API (See cgroups.txt). It allows to register multiple oom notification
> -delivery and gets notification when oom happens.
> +Memory cgroup implements OOM notifier using cgroup notification
> +API (See cgroups.txt). It allows to register multiple OOM notification
> +delivery and gets notification when OOM happens.
>
> To register a notifier, application need:
> - create an eventfd using eventfd(2)
> - open memory.oom_control file
> - - write string like "<event_fd> <memory.oom_control>" to cgroup.event_control
> + - write string like "<event_fd> <fd of memory.oom_control>" to
> + cgroup.event_control
>
> -Application will be notifier through eventfd when oom happens.
> +Application will be notified through eventfd when OOM happens.
> OOM notification doesn't work for root cgroup.
>
> -You can disable oom-killer by writing "1" to memory.oom_control file.
> +You can disable OOM-killer by writing "1" to memory.oom_control file.
> As.
to memory.oom_control file, as:
> #echo 1 > memory.oom_control
BTW: it would be a lot easier [for reviewing] if you could freeze (or merge) this version
and then apply fixes on top of it with a different (and shorter) patch.
Reviewed-by: Randy Dunlap <randy.dunlap@oracle.com>
---
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memcg: update documentation v7
Date: Wed, 14 Apr 2010 11:11:46 -0700 [thread overview]
Message-ID: <20100414111146.c2907cd7.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100414102221.2c540a0d.kamezawa.hiroyu@jp.fujitsu.com>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> Documentation/cgroups/memory.txt | 289 ++++++++++++++++++++++++++-------------
> 1 file changed, 197 insertions(+), 92 deletions(-)
>
> Index: mmotm-temp/Documentation/cgroups/memory.txt
> ===================================================================
> --- mmotm-temp.orig/Documentation/cgroups/memory.txt
> +++ mmotm-temp/Documentation/cgroups/memory.txt
> @@ -1,18 +1,15 @@
> Memory Resource Controller
>
> NOTE: The Memory Resource Controller has been generically been referred
> -to as the memory controller in this document. Do not confuse memory controller
> -used here with the memory controller that is used in hardware.
> + to as the memory controller in this document. Do not confuse memory
> + controller used here with the memory controller that is used in hardware.
>
> -Salient features
> -
> -a. Enable control of Anonymous, Page Cache (mapped and unmapped) and
> - Swap Cache memory pages.
> -b. The infrastructure allows easy addition of other types of memory to control
> -c. Provides *zero overhead* for non memory controller users
> -d. Provides a double LRU: global memory pressure causes reclaim from the
> - global LRU; a cgroup on hitting a limit, reclaims from the per
> - cgroup LRU
> +(For editors)
> +In this document:
> + When we mention a cgroup (cgroupfs's directory) with memory controller,
> + we call it "memory cgroup". When you see git-log and source code, you'll
> + see patch's title and function names tend to use "memcg".
> + In this document, we avoid to use it.
we avoid using it.
>
> Benefits and Purpose of the memory controller
> @@ -501,27 +605,28 @@ It's applicable for root and non-root cg
>
> memory.oom_control file is for OOM notification and other controls.
>
> -Memory controler implements oom notifier using cgroup notification
> -API (See cgroups.txt). It allows to register multiple oom notification
> -delivery and gets notification when oom happens.
> +Memory cgroup implements OOM notifier using cgroup notification
> +API (See cgroups.txt). It allows to register multiple OOM notification
> +delivery and gets notification when OOM happens.
>
> To register a notifier, application need:
> - create an eventfd using eventfd(2)
> - open memory.oom_control file
> - - write string like "<event_fd> <memory.oom_control>" to cgroup.event_control
> + - write string like "<event_fd> <fd of memory.oom_control>" to
> + cgroup.event_control
>
> -Application will be notifier through eventfd when oom happens.
> +Application will be notified through eventfd when OOM happens.
> OOM notification doesn't work for root cgroup.
>
> -You can disable oom-killer by writing "1" to memory.oom_control file.
> +You can disable OOM-killer by writing "1" to memory.oom_control file.
> As.
to memory.oom_control file, as:
> #echo 1 > memory.oom_control
BTW: it would be a lot easier [for reviewing] if you could freeze (or merge) this version
and then apply fixes on top of it with a different (and shorter) patch.
Reviewed-by: Randy Dunlap <randy.dunlap@oracle.com>
---
~Randy
--
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>
next prev parent reply other threads:[~2010-04-14 18:14 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 5:58 [PATCH] memcg: update documentation v3 KAMEZAWA Hiroyuki
2010-04-08 5:58 ` KAMEZAWA Hiroyuki
2010-04-08 17:32 ` Randy Dunlap
2010-04-08 17:32 ` Randy Dunlap
2010-04-08 23:50 ` KAMEZAWA Hiroyuki
2010-04-08 23:50 ` KAMEZAWA Hiroyuki
2010-04-09 1:26 ` Daisuke Nishimura
2010-04-09 1:26 ` Daisuke Nishimura
2010-04-09 1:45 ` KAMEZAWA Hiroyuki
2010-04-09 1:45 ` KAMEZAWA Hiroyuki
2010-04-09 2:11 ` Daisuke Nishimura
2010-04-09 2:11 ` Daisuke Nishimura
2010-04-09 3:01 ` KAMEZAWA Hiroyuki
2010-04-09 3:01 ` KAMEZAWA Hiroyuki
2010-04-09 4:45 ` [PATCH] memcg: update documentation v4 KAMEZAWA Hiroyuki
2010-04-09 4:45 ` KAMEZAWA Hiroyuki
2010-04-09 5:50 ` Daisuke Nishimura
2010-04-09 5:50 ` Daisuke Nishimura
2010-04-09 17:04 ` Randy Dunlap
2010-04-09 17:04 ` Randy Dunlap
2010-04-13 4:45 ` [PATCH] memcg: update documentation v5 KAMEZAWA Hiroyuki
2010-04-13 4:45 ` KAMEZAWA Hiroyuki
2010-04-13 6:04 ` Balbir Singh
2010-04-13 6:04 ` Balbir Singh
2010-04-13 6:20 ` KAMEZAWA Hiroyuki
2010-04-13 6:20 ` KAMEZAWA Hiroyuki
2010-04-13 6:48 ` Balbir Singh
2010-04-13 6:48 ` Balbir Singh
2010-04-13 6:58 ` [PATCH] memcg: update documentation v6 KAMEZAWA Hiroyuki
2010-04-13 6:58 ` KAMEZAWA Hiroyuki
2010-04-13 15:54 ` Randy Dunlap
2010-04-13 15:54 ` Randy Dunlap
2010-04-14 1:22 ` [PATCH] memcg: update documentation v7 KAMEZAWA Hiroyuki
2010-04-14 1:22 ` KAMEZAWA Hiroyuki
2010-04-14 18:11 ` Randy Dunlap [this message]
2010-04-14 18:11 ` Randy Dunlap
2010-04-15 0:34 ` [PATCH] memcg: update documentation v8 KAMEZAWA Hiroyuki
2010-04-15 0:34 ` KAMEZAWA Hiroyuki
2010-04-15 15:48 ` Randy Dunlap
2010-04-15 15:48 ` Randy Dunlap
2010-04-13 13:57 ` [PATCH] memcg: update documentation v5 Vivek Goyal
2010-04-13 13:57 ` Vivek Goyal
2010-04-13 14:03 ` Vivek Goyal
2010-04-13 14:03 ` Vivek Goyal
2010-04-13 15:08 ` Balbir Singh
2010-04-13 15:08 ` Balbir Singh
2010-04-13 15:16 ` Vivek Goyal
2010-04-13 15:16 ` Vivek Goyal
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=20100414111146.c2907cd7.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.