From: Johannes Weiner <jweiner@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <bsingharora@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: drain all stocks for the cgroup before read usage
Date: Thu, 8 Sep 2011 12:09:23 +0200 [thread overview]
Message-ID: <20110908100923.GD1316@redhat.com> (raw)
In-Reply-To: <20110908004906.GA8499@shutemov.name>
On Thu, Sep 08, 2011 at 03:49:07AM +0300, Kirill A. Shutemov wrote:
> On Thu, Sep 08, 2011 at 09:19:14AM +0900, KAMEZAWA Hiroyuki wrote:
> > > Should we have field 'ram' (or 'memory') for rss+cache in memory.stat?
> >
> > Why do you think so ?
>
> It may be useful for scripting purpose. Just an idea.
$ awk '/^cache/{mem+=$2} /^rss/{mem+=$2} END{print(mem)}' /sys/fs/cgroup/memory/memory.stat
1904500736
Am I missing something here?
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <jweiner@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <bsingharora@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: drain all stocks for the cgroup before read usage
Date: Thu, 8 Sep 2011 12:09:23 +0200 [thread overview]
Message-ID: <20110908100923.GD1316@redhat.com> (raw)
In-Reply-To: <20110908004906.GA8499@shutemov.name>
On Thu, Sep 08, 2011 at 03:49:07AM +0300, Kirill A. Shutemov wrote:
> On Thu, Sep 08, 2011 at 09:19:14AM +0900, KAMEZAWA Hiroyuki wrote:
> > > Should we have field 'ram' (or 'memory') for rss+cache in memory.stat?
> >
> > Why do you think so ?
>
> It may be useful for scripting purpose. Just an idea.
$ awk '/^cache/{mem+=$2} /^rss/{mem+=$2} END{print(mem)}' /sys/fs/cgroup/memory/memory.stat
1904500736
Am I missing something here?
--
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:[~2011-09-08 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 1:15 [PATCH] memcg: drain all stocks for the cgroup before read usage Kirill A. Shutemov
2011-09-04 1:15 ` Kirill A. Shutemov
2011-09-04 7:20 ` Paul Menage
2011-09-04 7:20 ` Paul Menage
2011-09-04 23:59 ` KAMEZAWA Hiroyuki
2011-09-04 23:59 ` KAMEZAWA Hiroyuki
2011-09-05 1:16 ` Daisuke Nishimura
2011-09-05 1:16 ` Daisuke Nishimura
2011-09-07 21:33 ` Kirill A. Shutemov
2011-09-07 21:33 ` Kirill A. Shutemov
2011-09-08 0:19 ` KAMEZAWA Hiroyuki
2011-09-08 0:19 ` KAMEZAWA Hiroyuki
2011-09-08 0:49 ` Kirill A. Shutemov
2011-09-08 0:49 ` Kirill A. Shutemov
2011-09-08 9:21 ` KAMEZAWA Hiroyuki
2011-09-08 9:21 ` KAMEZAWA Hiroyuki
2011-09-08 10:09 ` Johannes Weiner [this message]
2011-09-08 10:09 ` Johannes Weiner
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=20110908100923.GD1316@redhat.com \
--to=jweiner@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.