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]

Date:	Mon, 12 Nov 2007 20:41:10 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Ray Lee <ray-lk@...rabbit.org>
cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, Mel Gorman <mel@....ul.ie>,
	Andi Kleen <ak@...e.de>, Andy Whitcroft <apw@...dowen.org>
Subject: Re: x86_64: Make sparsemem/vmemmap the default memory model

On Mon, 12 Nov 2007, Ray Lee wrote:

> Discontig obviously needs to die. However, FlatMem is consistently
> faster, averaging about 2.1% better overall for your numbers above. Is
> the page allocator not, erm, a fast path, where that matters?
> 
> Order	Flat	Sparse	% diff
> 0	639	641	0.3

IMHO Order 0 currently matters most and the difference is negligible 
there.

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