[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1206722599.7883.119.camel@nimitz.home.sr71.net>
Date: Fri, 28 Mar 2008 09:43:19 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Christoph Lameter <clameter@....com>, Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Rusty Russell <rusty@...tcorp.com.au>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Yasunori Goto <y-goto@...fujitsu.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 3 of 4] sparsemem: reduce i386 PAE section size
On Thu, 2008-03-27 at 23:18 -0700, Jeremy Fitzhardinge wrote:
> Christoph Lameter wrote:
> > Only works on i386 if you either use sparsemem / vmemmap or not sparsemem
> > though. Is there any need for the other sparsemem memory models? Or could
> > we disable them like on x86_64?
>
> Probably, but I don't know what the tradeoffs are. All I want is
> hotplug memory.
Developers should probably learn the tradeoffs before they go start
poking around in code and sending patches. ;)
Maybe Christoph has a good idea what the tradeoffs are for the vmemmap
variant, but the table-based one is pretty simple. Smaller sections
mean that it costs you larger sparsemem structures and more bits in
page->flags. But, the smaller the section, the more mem_map[] you might
waste.
BTW, the current 1G sections were picked because all the hardware we
knew of at the time had 512MB dimms that had to be added in pairs. So,
we didn't ever have physical hotplug of less than that.
-- Dave
--
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