[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802201927440.26109@fbirervta.pbzchgretzou.qr>
Date: Wed, 20 Feb 2008 19:28:03 +0100 (CET)
From: Jan Engelhardt <jengelh@...putergmbh.de>
To: Pavel Machek <pavel@....cz>
cc: Balbir Singh <balbir@...ux.vnet.ibm.com>,
John Stoffel <john@...ffel.org>,
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 Feb 20 2008 18:19, Pavel Machek wrote:
>>
>> 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.
Yeah that must have been it when Windows says it found a new controller
after changing the mainboard underneath.
--
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