[Devel] Re: [PATCH -mmotm 4/4] memcg: Update memcg_test.txt to describe memory thresholds

[KAMEZAWA Hiroyuki]

On Sat, 20 Feb 2010 00:28:19 +0200
"Kirill A. Shutemov" <kirill at shutemov.name> wrote:

> Signed-off-by: Kirill A. Shutemov <kirill at shutemov.name>

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


> ---
>  Documentation/cgroups/memcg_test.txt |   21 +++++++++++++++++++++
>  1 files changed, 21 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/cgroups/memcg_test.txt b/Documentation/cgroups/memcg_test.txt
> index e011488..4d32e0e 100644
> --- a/Documentation/cgroups/memcg_test.txt
> +++ b/Documentation/cgroups/memcg_test.txt
> @@ -396,3 +396,24 @@ Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.
>  	memory.stat of both A and B.
>  	See 8.2 of Documentation/cgroups/memory.txt to see what value should be
>  	written to move_charge_at_immigrate.
> +
> + 9.10 Memory thresholds
> +	Memory controler implements memory thresholds using cgroups notification
> +	API. You can use Documentation/cgroups/cgroup_event_listener.c to test
> +	it.
> +
> +	(Shell-A) Create cgroup and run event listener
> +	# mkdir /cgroup/A
> +	# ./cgroup_event_listener /cgroup/A/memory.usage_in_bytes 5M
> +
> +	(Shell-B) Add task to cgroup and try to allocate and free memory
> +	# echo $$ >/cgroup/A/tasks
> +	# a="$(dd if=/dev/zero bs=1M count=10)"
> +	# a=
> +
> +	You will see message from cgroup_event_listener every time you cross
> +	the thresholds.
> +
> +	Use /cgroup/A/memory.memsw.usage_in_bytes to test memsw thresholds.
> +
> +	It's good idea to test root cgroup as well.
> -- 
> 1.6.6.2
> 
> 

_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers