search for: memsw

...che available > Mem: 201402642432 14413479936 75642777600 48586752 111346384896 185689632768 > Swap: 21474832384 31961088 21442871296 > [] cat /sys/fs/cgroup/memory/memory.max_usage_in_bytes > 273102151680 how can the max be so much higher than total, and this is not even memsw? either we're very tired and are overlooking something obvious, or there's something new to be learned ;) many thanks, stijn

...root 0 Sep 15 17:14 memory.kmem.tcp.usage_in_bytes -r--r--r-- 1 root root 0 Sep 15 17:14 memory.kmem.usage_in_bytes -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.limit_in_bytes -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.max_usage_in_bytes -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.memsw.failcnt -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.memsw.limit_in_bytes -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.memsw.max_usage_in_bytes -r--r--r-- 1 root root 0 Sep 15 17:14 memory.memsw.usage_in_bytes -rw-r--r-- 1 root root 0 Sep 15 17:14 memory.move_charge_at_immigrate -r--r--...

...eboot LXC container. 1) check that on HW node exists cgroups memory for container. [root@node]# cat /sys/fs/cgroup/memory/machine.slice/machine-lxc\\x2dpuppet.infra.scope/memory.limit_in_bytes 17179869184 [root@node]# cat /sys/fs/cgroup/memory/machine.slice/machine-lxc\\x2dpuppet.infra.scope/memory.memsw.limit_in_bytes 18203869184 In our case limit exists and set to 16Gb mem and 16+1 Gb for mem +swap Contaner name puppet.infra, substitute here your container name. 2) if exists - simple attach cgroups to libvirt_lxc pid : node# yum install libcgroup-tools node# cgclassify -g memory:machine.slice/m...

...;> Mem: 201402642432 14413479936 75642777600 48586752 111346384896 185689632768 >> Swap: 21474832384 31961088 21442871296 >> [] cat /sys/fs/cgroup/memory/memory.max_usage_in_bytes >> 273102151680 > how can the max be so much higher than total, and this is not even memsw? Binary K,M,G are 1024 multiples not 1000 so total seems a little low. > either we're very tired and are overlooking something obvious, or > there's something new to be learned ;) > > many thanks, > > stijn > _______________________________________________ > CentOS m...

...201402642432 14413479936 75642777600 48586752 111346384896 >> 185689632768 >> Swap: 21474832384 31961088 21442871296 >> [] cat /sys/fs/cgroup/memory/memory.max_usage_in_bytes >> 273102151680 > > how can the max be so much higher than total, and this is not even memsw? > > either we're very tired and are overlooking something obvious, or > there's something new to be learned ;) > Wonder if it's overcommitting memory.VMs do that, as a matter of course. mark

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo MemTotal: 9007199254740991 kB MemFree: 9007199224543267 kB MemAvailable: 12985680

...patched and non patched 2.6.32.41 kernel) > > When this is encountered, the memory usage across the whole server is > still within limits (not even hitting swap). > > The memory configuration for the cgroup/lxc is: > lxc.cgroup.memory.limit_in_bytes = 3000M > lxc.cgroup.memory.memsw.limit_in_bytes = 3128M > > Now, what is even more strange, is that when running under the > 2.6.32.28 kernel (both patched and unpatched), this problem doesn't > happen. However, there is a slight difference between the two kernels. > The 2.6.32.28 kernel gives a default of 0 in...