linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: John Stoffel <john@stoffel.org>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Andi Kleen <andi@firstfloor.org>,
	akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Document huge memory/cache overhead of memory controller in Kconfig
Date: Thu, 21 Feb 2008 12:22:07 +0530	[thread overview]
Message-ID: <47BD1F97.8030202@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080221154916.723fed49.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Wed, 20 Feb 2008 21:45:13 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 
>>> But for computers, limits is an expected and understood term, and for
>>> filesystems it's quotas.  So in this case, I *still* think you should
>>> be using the term "Memory Quota Controller" instead.  It just makes it
>>> clearer to a larger audience what you mean.
>>>
>> Memory Quota sounds very confusing to me. Usually a quota implies limits, but in
>> a true framework, one can also implement guarantees and shares.
>>
> This "cgroup memory contoller" is called as "Memory Resource Contoller"
> in my office ;)
> 
> How about Memory Resouce Contoller ?

That is a good name and believe me or not I was thinking of the same name.

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

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-02-21  6:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 12:23 [PATCH] Document huge memory/cache overhead of memory controller in Kconfig Andi Kleen
2008-02-20 12:52 ` Balbir Singh
2008-02-20 15:00   ` John Stoffel
2008-02-20 15:20     ` Balbir Singh
2008-02-20 15:49       ` Jan Engelhardt
2008-02-20 16:10         ` John Stoffel
2008-02-20 16:15           ` Balbir Singh
2008-02-20 17:00             ` Andi Kleen
2008-02-21  6:49             ` KAMEZAWA Hiroyuki
2008-02-21  6:52               ` Balbir Singh [this message]
2008-02-20 18:19         ` Pavel Machek
2008-02-20 18:28           ` Jan Engelhardt
2008-02-20 18:51             ` Pavel Machek
2008-02-21 14:46               ` KOSAKI Motohiro
2008-02-21 14:52                 ` Balbir Singh
2008-02-21 23:55                 ` Pavel Machek
2008-02-22  3:09                   ` KOSAKI Motohiro
2008-02-20 16:15       ` John Stoffel
2008-02-20 16:54       ` Ray Lee
2008-02-20 16:57     ` Andi Kleen
2008-02-21  4:35   ` Nick Piggin
2008-02-21  5:06     ` Balbir Singh
     [not found]       ` <200802211622.51751.nickpiggin@yahoo.com.au>
2008-02-21  5:46         ` Balbir Singh
2008-02-21 10:44       ` Andi Kleen
2008-02-22  4:41         ` Balbir Singh
2008-02-22  9:51           ` Andi Kleen
2008-02-22 12:14             ` Balbir Singh
2008-02-22 13:00               ` Andi Kleen
2008-02-22 15:47                 ` Balbir Singh
2008-02-21 10:37     ` Andi Kleen
2008-02-21 11:03       ` Balbir Singh
2008-02-22  6:59         ` KAMEZAWA Hiroyuki
2008-02-22  7:06           ` Balbir Singh

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=47BD1F97.8030202@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@osdl.org \
    --cc=andi@firstfloor.org \
    --cc=jengelh@computergmbh.de \
    --cc=john@stoffel.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).