From: Glauber Costa <glommer@parallels.com>
To: David Rientjes <rientjes@google.com>
Cc: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Gao feng <gaofeng@cn.fujitsu.com>,
hannes@cmpxchg.org, mhocko@suse.cz, bsingharora@gmail.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, linux-mm@kvack.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg
Date: Thu, 31 May 2012 12:29:01 +0400 [thread overview]
Message-ID: <4FC72BCD.7040403@parallels.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205302314190.25774@chino.kir.corp.google.com>
On 05/31/2012 10:17 AM, David Rientjes wrote:
>> > 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.
I disagree. For simple applications, yes. For full containers, the
cgroup in which it lives in is considered part of the external world.
It should not have any kind of access to it.
Also, tools need to work transparently.
That's the same case with /proc/stat, used for top. We can't expect
people to recode top to work on containerized environments.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-31 8:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 2:56 [PATCH] meminfo: show /proc/meminfo base on container's memcg Gao feng
2012-05-29 8:24 ` Glauber Costa
2012-05-30 21:38 ` David Rientjes
2012-05-30 23:20 ` Kirill A. Shutemov
2012-05-31 0:35 ` David Rientjes
2012-05-31 0:08 ` Kamezawa Hiroyuki
2012-05-31 0:22 ` KOSAKI Motohiro
2012-05-31 0:33 ` Kamezawa Hiroyuki
2012-05-31 0:44 ` David Rientjes
2012-05-31 0:53 ` Kamezawa Hiroyuki
2012-05-31 1:31 ` David Rientjes
2012-05-31 2:33 ` Kamezawa Hiroyuki
2012-05-31 5:02 ` David Rientjes
2012-05-31 5:36 ` Kamezawa Hiroyuki
2012-05-31 6:17 ` David Rientjes
2012-05-31 6:23 ` KOSAKI Motohiro
2012-05-31 6:28 ` David Rientjes
2012-05-31 6:37 ` KOSAKI Motohiro
2012-05-31 6:56 ` David Rientjes
2012-05-31 7:09 ` KOSAKI Motohiro
2012-05-31 7:35 ` David Rientjes
2012-05-31 7:42 ` KOSAKI Motohiro
2012-05-31 7:57 ` Johannes Weiner
2012-05-31 7:58 ` Gao feng
2012-05-31 8:32 ` Glauber Costa
2012-05-31 8:51 ` Kamezawa Hiroyuki
2012-05-31 8:59 ` Glauber Costa
2012-05-31 8:55 ` Gao feng
2012-05-31 8:56 ` Glauber Costa
2012-05-31 7:07 ` Kamezawa Hiroyuki
2012-05-31 7:23 ` KOSAKI Motohiro
2012-05-31 8:29 ` Glauber Costa [this message]
2012-06-07 23:18 ` Zhu Yanhai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC72BCD.7040403@parallels.com \
--to=glommer@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=gaofeng@cn.fujitsu.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).