linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Balaji Rao <balajirrao@gmail.com>,
	linux-kernel@vger.kernel.org, containers@lists.osdl.org,
	balbir@in.ibm.com, dhaval@linux.vnet.ibm.com
Subject: Re: [RFC][-mm] [2/2] Simple stats for memory resource controller
Date: Thu, 27 Mar 2008 00:23:36 +0530	[thread overview]
Message-ID: <47EA9BB0.3030202@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830803261152j1973e3c8oa82181a830f89260@mail.gmail.com>

Paul Menage wrote:
> On Wed, Mar 26, 2008 at 11:18 AM, Balaji Rao <balajirrao@gmail.com> wrote:
>>         [MEM_CGROUP_STAT_RSS] = { "rss", PAGE_SIZE, },
>>  +       [MEM_CGROUP_STAT_PGIN_COUNT] = {"page_in_count", 1, },
>>  +       [MEM_CGROUP_STAT_PGOUT_COUNT] = {"page_out_count", 1, },
>>   };
>>
> 
> Should these be called "pgpgin" and "pgpgout" for consistency with /proc/vmstat?
> 
> Paul

Yes, that is a good name. We also want to instantaneous metrics like
page_in_count per second and page_out_count per second to help the administrator
monitor what is going on within the tasks in the cgroup w.r.t. memory.


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  reply	other threads:[~2008-03-26 18:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 18:18 [RFC][-mm] [2/2] Simple stats for memory resource controller Balaji Rao
2008-03-26 18:52 ` Paul Menage
2008-03-26 18:53   ` Balbir Singh [this message]
2008-03-26 18:54 ` Balbir Singh
  -- strict thread matches above, loose matches on Subject: below --
2008-04-05 18:10 Balaji Rao
2008-04-06  6:23 ` Balbir Singh
2008-04-14 14:39 ` Balbir Singh
2008-04-14 14:40   ` Balbir Singh
2008-04-28 16:00   ` Balaji Rao
2008-04-28 16:40     ` Andrew Morton
2008-04-28 18:03       ` Balbir Singh
2008-04-29  5:42         ` KAMEZAWA Hiroyuki

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=47EA9BB0.3030202@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=balajirrao@gmail.com \
    --cc=balbir@in.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@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).