linux-kernel - Re: [Patch] Allocate sparse vmemmap block above 4G

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] [day] [month] [year] [list]

Message-Id: <1194455550.7078.58.camel@localhost>
Date:	Wed, 07 Nov 2007 09:12:30 -0800
From:	Dave Hansen <haveblue@...ibm.com>
To:	Zou Nan hai <nanhai.zou@...el.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, Suresh.b.siddha@...el.com
Subject: Re: [Patch] Allocate sparse vmemmap block above 4G

On Wed, 2007-11-07 at 15:07 +0800, Zou Nan hai wrote:
> Try to allocate sparse vmemmap block above 4G on x64 system.
> 
> On some single node x64 system with huge amount of physical memory e.g
> 64G. the memmap size maybe very big. 

Could we just change the default bootmem behavior to allocate top-down?

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