linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: hannes@cmpxchg.org, kamezawa.hiroyu@jp.fujitsu.com,
	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: Wed, 30 May 2012 14:38:25 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1205301433490.9716@chino.kir.corp.google.com> (raw)
In-Reply-To: <1338260214-21919-1-git-send-email-gaofeng@cn.fujitsu.com>

On Tue, 29 May 2012, Gao feng wrote:

> cgroup and namespaces are used for creating containers but some of
> information is not isolated/virtualized. This patch is for isolating /proc/meminfo
> information per container, which uses memory cgroup. By this, top,free
> and other tools under container can work as expected(show container's
> usage) without changes.
> 
> This patch is a trial to show memcg's info in /proc/meminfo if 'current'
> is under a memcg other than root.
> 
> we show /proc/meminfo base on container's memory cgroup.
> because there are lots of info can't be provide by memcg, and
> the cmds such as top, free just use some entries of /proc/meminfo,
> we replace those entries by memory cgroup.
> 
> if container has no memcg, we will show host's /proc/meminfo
> as before.
> 
> there is no idea how to deal with Buffers,I just set it zero,
> It's strange if Buffers bigger than MemTotal.
> 
> Signed-off-by: Gao feng <gaofeng@cn.fujitsu.com>

Nack, this type of thing was initially tried with cpusets when a thread 
was bound to a subset of nodes, i.e. only show the total amount of memory 
spanned by those nodes.

For your particular interest, this information is already available 
elsewhere: memory.limit_in_bytes and memory.usage_in_bytes and that should 
be the interface where this is attained via /proc/cgroups.

Why?  Because the information exported by /proc/meminfo is considered by 
applications to be static whereas the limit of a memcg may change without 
any knowledge of the application.  Applications which need to know the 
amount of memory they are constrained to are assuming that there are no 
other consumers of memory on the system and thus they should be written to 
understand memcg limits just like they should understand cpusets (through 
either /proc/cgroups or /proc/cpuset).

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

  parent reply	other threads:[~2012-05-30 21:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29  2:56 Gao feng
2012-05-29  8:24 ` Glauber Costa
2012-05-30 21:38 ` David Rientjes [this message]
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
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=alpine.DEB.2.00.1205301433490.9716@chino.kir.corp.google.com \
    --to=rientjes@google.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=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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