linux-kernel - Re: [RFC 0/2] Delay initializing of large sections of memory

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]

Message-ID: <51C9DEC1.6030602@zytor.com>
Date:	Tue, 25 Jun 2013 11:17:37 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Mike Travis <travis@....com>
CC:	Yinghai Lu <yinghai@...nel.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Nathan Zimmer <nzimmer@....com>, Robin Holt <holt@....com>,
	Rob Landley <rob@...dley.net>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	linux-doc@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 0/2] Delay initializing of large sections of memory

On 06/25/2013 10:35 AM, Mike Travis wrote:
> 
> The two params that I couldn't figure out how to provide except via kernel
> param option was the memory block size (128M or 2G) and the physical
> address space per node.  The other 3 params can be automatically
> setup by a script when the total system size is known.  As soon as we
> verify on the 32TB system and surmise what will be needed for 64TB,
> then those 3 params can probably disappear.
> 

"Setup by script" is a no-go.  You *have* the total system size already,
it is in the e820 tables (anything which isn't in e820 is hotplug, that
automagically gets deferred.)

However, please consider Ingo's counterproposal of doing this via the
buddy allocator, i.e. hugepages being broken on demand.  That is a
*very* powerful model, although would require more infrastructure.

	-hpa


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