On Feb 20 2008 20:50, Balbir Singh wrote: >John Stoffel wrote: >> 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. >If you look through some of the references in the document, we've >listed our plans to support other categories of memory as well. >Hence it's called a memory controller > >> Also, the Kconfig name "CGROUP_MEM_CONT" is just wrong, it should >> be "CGROUP_MEM_CONTROLLER", just spell it out so it's clear what's >> up. > >This has some history as well. Control groups was called containers >earlier. That way a name like CGROUP_MEM_CONT could stand for cgroup >memory container or cgroup memory controller. CONT is shorthand for "continue" ;-) (SIGCONT, f.ex.), ctrl or ctrlr it is for controllers (comes from Solaris iirc.) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
