No limitation in physical memory in cgroups

KAMEZAWA Hiroyuki kamezawa.hiroyu at jp.fujitsu.com
Thu May 21 19:56:22 PDT 2009


On Fri, 22 May 2009 10:31:39 +0800
anqin <anqin.qin at gmail.com> wrote:

> > Are you booting with noswapaccount as a boot parameter?
> >
> 
> hmm....  I am not sure. I just compiled the kernel at default.
> Where can I check the boot parameter? In /boot/grub/menu.list,
> no the parameter yet.
> 
Hmm. When 

CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y

And no special boot option, the memory cgroup directory will be.
==
[root at bluextal cgroup]# ls /cgroups/A/
memory.failcnt                   memory.memsw.usage_in_bytes
memory.force_empty               memory.stat
memory.limit_in_bytes            memory.swappiness
memory.max_usage_in_bytes        memory.usage_in_bytes
memory.memsw.failcnt             memory.use_hierarchy
memory.memsw.limit_in_bytes      notify_on_release
memory.memsw.max_usage_in_bytes  tasks
==

You can see memory.memsw.* for limiting mem+swap usage.
This memory.memsw. files disappears when you set "noswapaccount" boot option...

I can only say "counld you confirm again ?"
 config, the kernel version etc...

Sorry for no help.

Bye.
-Kame




More information about the Containers mailing list