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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Jörn Engel <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- References:
- x86_64: Make sparsemem/vmemmap the default memory model
- From: Christoph Lameter <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Andi Kleen <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Christoph Lameter <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Andi Kleen <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: Christoph Lameter <[email protected]>
- Re: x86_64: Make sparsemem/vmemmap the default memory model
- From: "Ray Lee" <[email protected]>
- x86_64: Make sparsemem/vmemmap the default memory model
- Prev by Date: Re: [PATCH] module loader should not complain about unknown symbol
- Next by Date: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB
- Previous by thread: Re: x86_64: Make sparsemem/vmemmap the default memory model
- Next by thread: Re: x86_64: Make sparsemem/vmemmap the default memory model
- Index(es):