From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards Date: Fri, 22 Apr 2011 16:33:05 -0500 Message-ID: <1303507985.2590.47.camel@mulgrave.site> References: <1303337718.2587.51.camel@mulgrave.site> <20110421221712.9184.A69D9226@jp.fujitsu.com> <1303403847.4025.11.camel@mulgrave.site> <1303411537.9048.3583.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Christoph Lameter , KOSAKI Motohiro , David Rientjes , Pekka Enberg , Michal Hocko , Andrew Morton , Hugh Dickins , linux-mm@kvack.org, LKML , linux-parisc@vger.kernel.org, Ingo Molnar , x86 maintainers , Tejun Heo , Mel Gorman To: Dave Hansen Return-path: In-Reply-To: <1303411537.9048.3583.camel@nimitz> List-ID: List-Id: linux-parisc.vger.kernel.org On Thu, 2011-04-21 at 11:45 -0700, Dave Hansen wrote: > On Thu, 2011-04-21 at 13:33 -0500, Christoph Lameter wrote: > > http://www.linux-mips.org/archives/linux-mips/2008-08/msg00154.html > > By the way, this reference is actively wrong for parisc (having just debugged the problem). The basic issue is that until we start paging, we have the kernel and some memory beyond it barely covered with the pg0 page table set up in head.S On our systems, that extends out to 16MB. SPARSEMEM is much more bootmem resource greedy than DISCONTIGMEM, so if we actually call sparse_init() before we have the page tables set up, we fall off the end of our 16MB mapping and go boom. For us, therefore, we can't call sparse_init() until we have our proper page tables in place. James