Messages in this thread | | | Date | Wed, 30 May 2012 23:28:54 -0700 (PDT) | From | David Rientjes <> | Subject | Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg |
| |
On Thu, 31 May 2012, KOSAKI Motohiro wrote:
> > An application should always know the cgroup that its attached to and be > > able to read its state using the command that I gave earlier. > > No. you don't need why userland folks want namespaces. Even though you don't > need namespaces. It doesn't good reason to refuse another use case. >
This is tangent to the discussion, we need to revisit why an application other than a daemon managing a set of memcgs would ever need to know the information in /proc/meminfo. No use-case was ever presented in the changelog and its not clear how this is at all relevant. So before changing the kernel, please describe how this actually matters in a real- world scenario.
| |