linux-kernel - Re: [RFC 06/23] mm/memblock: Add memblock early memory allocation apis

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 13 Oct 2013 19:00:59 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Tejun Heo <tj@...nel.org>
Cc:	Santosh Shilimkar <santosh.shilimkar@...com>,
	grygorii.strashko@...com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
	yinghai@...nel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC 06/23] mm/memblock: Add memblock early memory allocation
	apis

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.
--
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/