Linux Container Development
 help / color / mirror / Atom feed
From: yamamoto-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org (YAMAMOTO Takashi)
To: balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	minoura-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org
Subject: Re: [RFC] [PATCH] memory controller statistics
Date: Tue,  9 Oct 2007 07:55:28 +0900 (JST)	[thread overview]
Message-ID: <20071008225528.7A0481BF486@siro.lan> (raw)
In-Reply-To: Your message of "Sun, 07 Oct 2007 11:26:59 +0530" <4708752B.9080107-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

> Forgot to mention one other detail, could we track the statistics
> in bytes? We track usage and limit in bytes currently. I am open
> to opinions on this, but the last time we discussed numbers,
> tracking bytes was the preferred approach.

while /proc/vmstat and others uses number of pages?
IMO, numbers of pages make more sense for this kind of statistics.

however, if there's a consensus, i can follow.  after all,
it's merely a matter of taste.

YAMAMOTO Takashi

  parent reply	other threads:[~2007-10-08 22:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  3:39 [RFC] [PATCH] memory controller statistics YAMAMOTO Takashi
     [not found] ` <20070907033942.4A6541BFA52-Pcsii4f/SVk@public.gmane.org>
2007-09-07  5:02   ` KAMEZAWA Hiroyuki
     [not found]     ` <20070907140234.4fe1075d.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-09-07  5:38       ` YAMAMOTO Takashi
2007-09-07  9:55   ` Balbir Singh
     [not found]     ` <46E12020.1060203-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-09-10  0:32       ` 箕浦真
     [not found]         ` <kk5tzq39x7h.fsf-VZKBDE94do7Xw16qUzMy135BbFPdSy0r@public.gmane.org>
2007-09-10  8:26           ` Balbir Singh
2007-09-10 23:21       ` Paul Menage
     [not found]         ` <6599ad830709101621r2f1763cfpa0924f884d0ee2c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-11  2:39           ` Balbir Singh
2007-09-26  1:48       ` YAMAMOTO Takashi
     [not found]         ` <20070926014843.161E61BFA33-Pcsii4f/SVk@public.gmane.org>
2007-09-26  3:16           ` Balbir Singh
2007-10-04  5:13   ` YAMAMOTO Takashi
     [not found]     ` <20071004051332.9BE2C1BF95B-Pcsii4f/SVk@public.gmane.org>
2007-10-05  3:51       ` Balbir Singh
     [not found]         ` <4705B4AA.4070604-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-10-07  5:56           ` Balbir Singh
     [not found]             ` <4708752B.9080107-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-10-08 22:55               ` YAMAMOTO Takashi [this message]
     [not found]                 ` <20071008225528.7A0481BF486-Pcsii4f/SVk@public.gmane.org>
2007-10-09  3:11                   ` Balbir Singh
2007-10-10  1:01       ` YAMAMOTO Takashi
     [not found]         ` <20071010010117.D9A821BEEE7-Pcsii4f/SVk@public.gmane.org>
2007-10-10  6:44           ` KAMEZAWA Hiroyuki
     [not found]             ` <20071010154415.951943e7.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-10-10  8:19               ` YAMAMOTO Takashi

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=20071008225528.7A0481BF486@siro.lan \
    --to=yamamoto-jcdqpdek3idl9jvzuh4aog@public.gmane.org \
    --cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=minoura-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org \
    /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