Re: [PATCH] Document huge memory/cache overhead of memory controller in Kconfig

[Pavel Machek]

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/