From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) by kanga.kvack.org (Postfix) with ESMTP id AEA536B0031 for ; Sun, 13 Oct 2013 14:42:18 -0400 (EDT) Received: by mail-pa0-f41.google.com with SMTP id bj1so6615068pad.0 for ; Sun, 13 Oct 2013 11:42:18 -0700 (PDT) Received: by mail-qc0-f180.google.com with SMTP id p19so4423589qcv.11 for ; Sun, 13 Oct 2013 11:42:15 -0700 (PDT) Date: Sun, 13 Oct 2013 14:42:12 -0400 From: Tejun Heo Subject: Re: [RFC 06/23] mm/memblock: Add memblock early memory allocation apis Message-ID: <20131013184212.GA18075@htj.dyndns.org> References: <1381615146-20342-1-git-send-email-santosh.shilimkar@ti.com> <1381615146-20342-7-git-send-email-santosh.shilimkar@ti.com> <20131013175648.GC5253@mtj.dyndns.org> <20131013180058.GG25034@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131013180058.GG25034@n2100.arm.linux.org.uk> Sender: owner-linux-mm@kvack.org List-ID: To: Russell King - ARM Linux Cc: Santosh Shilimkar , grygorii.strashko@ti.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , yinghai@kernel.org, linux-arm-kernel@lists.infradead.org On Sun, Oct 13, 2013 at 07:00:59PM +0100, Russell King - ARM Linux wrote: > On Sun, Oct 13, 2013 at 01:56:48PM -0400, Tejun Heo wrote: > > Hello, > > > > On Sat, Oct 12, 2013 at 05:58:49PM -0400, Santosh Shilimkar wrote: > > > Introduce memblock early memory allocation APIs which allow to support > > > LPAE extension on 32 bits archs. More over, this is the next step > > > > LPAE isn't something people outside arm circle would understand. > > Let's stick to highmem. > > LPAE != highmem. Two totally different things, unless you believe > system memory always starts at physical address zero, which is very > far from the case on the majority of ARM platforms. > > So replacing LPAE with "highmem" is pure misrepresentation and is > inaccurate. PAE might be a better term, and is also the x86 term > for this. Ah, right, forgot about the base address. Let's please spell out the requirements then. Briefly explaining both aspects (non-zero base addr & highmem) and why the existing bootmem based interfaced can't serve them would be helpful to later readers. Thanks. -- tejun -- 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