[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080221154916.723fed49.kamezawa.hiroyu@jp.fujitsu.com>
Date: Thu, 21 Feb 2008 15:49:16 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: balbir@...ux.vnet.ibm.com
Cc: John Stoffel <john@...ffel.org>,
Jan Engelhardt <jengelh@...putergmbh.de>,
Andi Kleen <andi@...stfloor.org>, akpm@...l.org,
torvalds@...l.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] Document huge memory/cache overhead of memory
controller in Kconfig
On Wed, 20 Feb 2008 21:45:13 +0530
Balbir Singh <balbir@...ux.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 ?
-Kame
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists