Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg

[KOSAKI Motohiro]

(5/31/12 2:17 AM), David Rientjes wrote:
> On Thu, 31 May 2012, Kamezawa Hiroyuki wrote:
>
> > > The bottomline is that /proc/meminfo is one of many global resource state
> > > interfaces and doesn't imply that every thread has access to the full
> > > resources.  It never has.  It's very simple for another thread to consume
> > > a large amount of memory as soon as your read() of /proc/meminfo completes
> > > and then that information is completely bogus.
> >
> > Why you need to discuss this here ? We know all information are snapshot.
>
> MemTotal is usually assumed to be static from /proc/meminfo and could now
> change radically without notification to the application.
>
> > Hmm....maybe need to mount cgroup in the container (again) and get an access
> > to cgroup
> > hierarchy and find the cgroup it belongs to......if it's allowed.
>
> 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/