From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 20 Feb 2008 18:19:12 +0000 From: Pavel Machek Subject: Re: [PATCH] Document huge memory/cache overhead of memory controller in Kconfig Message-ID: <20080220181911.GA4760@ucw.cz> References: <20080220122338.GA4352@basil.nowhere.org> <47BC2275.4060900@linux.vnet.ibm.com> <18364.16552.455371.242369@stoffel.org> <47BC4554.10304@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org Return-Path: To: Jan Engelhardt Cc: Balbir Singh , John Stoffel , Andi Kleen , akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: Hi! > >> I know this is a pedantic comment, but why the heck is it called such > >> a generic term as "Memory Controller" which doesn't give any > >> indication of what it does. > >> > >> Shouldn't it be something like "Memory Quota Controller", or "Memory > >> Limits Controller"? > > > >It's called the memory controller since it controls the amount of > >memory that a user can allocate (via limits). The generic term for > >any resource manager plugged into cgroups is a controller. > > For ordinary desktop people, memory controller is what developers > know as MMU or sometimes even some other mysterious piece of silicon > inside the heavy box. Actually I'd guess 'memory controller' == 'DRAM controller' == part of northbridge that talks to DRAM. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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: email@kvack.org