linux-kernel - Re: x86_64: Make sparsemem/vmemmap the default memory model

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: <20071115141212.acb215f1.akpm@linux-foundation.org>
Date:	Thu, 15 Nov 2007 14:12:12 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Christoph Lameter <clameter@....com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org, mel@....ul.ie,
	ak@...e.de, apw@...dowen.org
Subject: Re: x86_64: Make sparsemem/vmemmap the default memory model

On Mon, 12 Nov 2007 19:42:31 -0800 (PST)
Christoph Lameter <clameter@....com> wrote:

> x86_64: Make sparsemem/vmemmap the default memory model
> 
> Use sparsemem as the only memory model for UP, SMP and NUMA.
> Measurements indicate that DISCONTIGMEM has a higher overhead
> than sparsemem. And FLATMEMs benefits are minimal. So I think its
> best to simply standardize on sparsemem.

Unfortunately some loon has gone and merged the i386 and x86_64 Kconfig
files.  I was fixing that up but I worry what effects these Kconfig changes
might have on, for example, i386 NUMA setups.

So I'll duck this version, sorry.
-
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/