From: "Ray Lee" <ray-lk@madrabbit.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>,
Andi Kleen <ak@suse.de>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: x86_64: Make sparsemem/vmemmap the default memory model
Date: Mon, 12 Nov 2007 20:27:34 -0800 [thread overview]
Message-ID: <2c0942db0711122027m5b11502cveded5705c0bc4f64@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711121940410.30269@schroedinger.engr.sgi.com>
On Nov 12, 2007 7:42 PM, Christoph Lameter <clameter@sgi.com> wrote:
> Ok here is the patch to remove DISCONTIG and FLATMEM
>
> 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.
>
> Results of page allocator tests (test can be had via git from slab git
> tree branch tests)
>
> Measurements in cycle counts. 1000 allocations were performed and then the
> average cycle count was calculated.
>
> Order FlatMem Discontig SparseMem
> 0 639 665 641
> 1 567 647 593
> 2 679 774 692
> 3 763 967 781
> 4 961 1501 962
> 5 1356 2344 1392
> 6 2224 3982 2336
> 7 4869 7225 5074
> 8 12500 14048 12732
> 9 27926 28223 28165
> 10 58578 58714 58682
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
1 567 593 4.4
2 679 692 1.9
3 763 781 2.3
4 961 962 0.1
5 1356 1392 2.6
6 2224 2336 4.8
7 4869 5074 4.0
8 12500 12732 1.8
9 27926 28165 0.8
10 58578 58682 0.2
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-11-13 4:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 23:52 Christoph Lameter
2007-11-12 23:59 ` Andi Kleen
2007-11-13 0:42 ` Christoph Lameter
2007-11-13 0:49 ` Andi Kleen
2007-11-13 3:42 ` Christoph Lameter
2007-11-13 4:27 ` Ray Lee [this message]
2007-11-13 4:41 ` Christoph Lameter
2007-11-13 20:41 ` Jörn Engel
2007-11-13 21:52 ` Christoph Lameter
2007-11-13 22:30 ` Jörn Engel
2007-11-15 22:12 ` Andrew Morton
2007-11-16 2:24 ` Christoph Lameter
2007-11-16 2:52 ` Andrew Morton
2007-11-16 3:55 ` x86_64: Make sparsemem/vmemmap the default memory model V2 Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c0942db0711122027m5b11502cveded5705c0bc4f64@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox