On 07/20/2015 02:17 PM, Michal Hocko wrote: > On Fri 17-07-15 10:16:25, Nikolay Borisov wrote: >> >> >> On 07/17/2015 10:13 AM, Michal Hocko wrote: >>> On Fri 17-07-15 00:21:51, Nikolay Borisov wrote: > [...] >>>> In my particular use case I have to query the memcg's various counters to expose >>>> them to the user in a different way than via the cgroup files >>>> (memory.limit_in_bytes etc). >>> >>> Why is the regular interface not sufficient? >> >> In my particular case I'm interested in playing with the contents of >> /proc/meminfo, so that processes running inside a cgroup only see the >> the system as defined by the memcg restrictions > > I assume that this is an attempt to containerize /proc/meminfo. I am not > sure this is a great idea. There are counters which do not have memcg > specific counterpart or such a counterpart would be missleading (e.g. > slab, swap statistics). Why would swap be misleading? What about memsw.limit_in_bytes - memory.limit_in_bytes for the total swap and calculating the swap usage based on memory.memsw.max_usage_in_bytes - memory.usage_in_bytes ? > > Is this an out-of-tree project or you are trying to push your changes to > the Linus tree somewhere? I haven't noticed such patches. It's an out-of-tree project and I'm well aware there are certain numbers which do not correspond 1:1 but that is fine for my use case. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
