summaryrefslogtreecommitdiffstats
path: root/mm/page-writeback.c
diff options
context:
space:
mode:
authorKAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>2009-01-07 18:08:26 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2009-01-08 08:31:09 -0800
commitfee7b548e6f2bd4bfd03a1a45d3afd593de7d5e9 (patch)
tree90a8b610298013c6ce2d9bb7970b8e6d2a66f488 /mm/page-writeback.c
parentc772be939e078afd2505ede7d596a30f8f61de95 (diff)
downloadkernel-crypto-fee7b548e6f2bd4bfd03a1a45d3afd593de7d5e9.tar.gz
kernel-crypto-fee7b548e6f2bd4bfd03a1a45d3afd593de7d5e9.tar.xz
kernel-crypto-fee7b548e6f2bd4bfd03a1a45d3afd593de7d5e9.zip
memcg: show real limit under hierarchy mode
Show "real" limit of memcg. This helps my debugging and maybe useful for users. While testing hierarchy like this mount -t cgroup none /cgroup -t memory mkdir /cgroup/A set use_hierarchy==1 to "A" mkdir /cgroup/A/01 mkdir /cgroup/A/01/02 mkdir /cgroup/A/01/03 mkdir /cgroup/A/01/03/04 mkdir /cgroup/A/08 mkdir /cgroup/A/08/01 .... and set each own limit to them, "real" limit of each memcg is unclear. This patch shows real limit by checking all ancestors. Changelog: (v1) -> (v2) - remove "if" and use "min(a,b)" Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/page-writeback.c')
0 files changed, 0 insertions, 0 deletions