| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 31 May 2012 11:33:37 +0900 From: Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: David Rientjes <rientjes@...gle.com> CC: KOSAKI Motohiro <kosaki.motohiro@...il.com>, Gao feng <gaofeng@...fujitsu.com>, hannes@...xchg.org, mhocko@...e.cz, bsingharora@...il.com, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, cgroups@...r.kernel.org, linux-mm@...ck.org, containers@...ts.linux-foundation.org Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg (2012/05/31 10:31), David Rientjes wrote: > On Thu, 31 May 2012, Kamezawa Hiroyuki wrote: > >>>> My test with sysfs node's meminfo seems to work... >>>> >>>> [root@...00-1 qqm]# mount --bind /sys/devices/system/node/node0/meminfo >>>> /proc/meminfo >>>> [root@...00-1 qqm]# cat /proc/meminfo >>>> >>>> Node 0 MemTotal: 8379636 kB >>> >>> This doesn't seem like a good idea unless the application supports the >>> "Node 0" prefix in /proc/meminfo. >>> >> Of course, /cgroup/memory/..../memory.meminfo , a new file, will use the same >> format of /proc/meminfo. Above is just an example of bind-mount. >> > > It's not just a memcg issue, it would also be a cpusets issue. I think you can add cpuset.meminfo. Thanks, -Kame -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists