Re: Access rules for current->memcg

[Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>]

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).

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.
-- 
Michal Hocko
SUSE Labs