From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catalin Marinas Subject: Re: [RFC PATCH v2 06/11] ARM64: mm: Restore memblock limit when map_mem finished. Date: Thu, 16 May 2013 14:52:34 +0100 Message-ID: <20130516135233.GB18308@arm.com> References: <1368006763-30774-1-git-send-email-steve.capper@linaro.org> <1368006763-30774-7-git-send-email-steve.capper@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1368006763-30774-7-git-send-email-steve.capper@linaro.org> Sender: owner-linux-mm@kvack.org To: Steve Capper Cc: "linux-mm@kvack.org" , "x86@kernel.org" , "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Michal Hocko , Ken Chen , Mel Gorman , Will Deacon , "patches@linaro.org" List-Id: linux-arch.vger.kernel.org On Wed, May 08, 2013 at 10:52:38AM +0100, Steve Capper wrote: > In paging_init the memblock limit is set to restrict any addresses > returned by early_alloc to fit within the initial direct kernel > mapping in swapper_pg_dir. This allows map_mem to allocate puds, > pmds and ptes from the initial direct kernel mapping. > > The limit stays low after paging_init() though, meaning any > bootmem allocations will be from a restricted subset of memory. > Gigabyte huge pages, for instance, are normally allocated from > bootmem as their order (18) is too large for the default buddy > allocator (MAX_ORDER = 11). > > This patch restores the memblock limit when map_mem has finished, > allowing gigabyte huge pages (and other objects) to be allocated > from all of bootmem. > > Signed-off-by: Steve Capper Acked-by: Catalin Marinas -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fw-tnat.cambridge.arm.com ([217.140.96.21]:49543 "EHLO cam-smtp0.cambridge.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752977Ab3EPOAK (ORCPT ); Thu, 16 May 2013 10:00:10 -0400 Date: Thu, 16 May 2013 14:52:34 +0100 From: Catalin Marinas Subject: Re: [RFC PATCH v2 06/11] ARM64: mm: Restore memblock limit when map_mem finished. Message-ID: <20130516135233.GB18308@arm.com> References: <1368006763-30774-1-git-send-email-steve.capper@linaro.org> <1368006763-30774-7-git-send-email-steve.capper@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1368006763-30774-7-git-send-email-steve.capper@linaro.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Steve Capper Cc: "linux-mm@kvack.org" , "x86@kernel.org" , "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Michal Hocko , Ken Chen , Mel Gorman , Will Deacon , "patches@linaro.org" Message-ID: <20130516135234.mnhwwGiX9e4IviYy2ZKqT2ozFJsu12FgM9evoSrKlmk@z> On Wed, May 08, 2013 at 10:52:38AM +0100, Steve Capper wrote: > In paging_init the memblock limit is set to restrict any addresses > returned by early_alloc to fit within the initial direct kernel > mapping in swapper_pg_dir. This allows map_mem to allocate puds, > pmds and ptes from the initial direct kernel mapping. > > The limit stays low after paging_init() though, meaning any > bootmem allocations will be from a restricted subset of memory. > Gigabyte huge pages, for instance, are normally allocated from > bootmem as their order (18) is too large for the default buddy > allocator (MAX_ORDER = 11). > > This patch restores the memblock limit when map_mem has finished, > allowing gigabyte huge pages (and other objects) to be allocated > from all of bootmem. > > Signed-off-by: Steve Capper Acked-by: Catalin Marinas