All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, mel@csn.ul.ie,
	ak@suse.de, apw@shadowen.org
Subject: Re: x86_64: Make sparsemem/vmemmap the default memory model
Date: Thu, 15 Nov 2007 14:12:12 -0800	[thread overview]
Message-ID: <20071115141212.acb215f1.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711121940410.30269@schroedinger.engr.sgi.com>

On Mon, 12 Nov 2007 19:42:31 -0800 (PST)
Christoph Lameter <clameter@sgi.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.

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, mel@csn.ul.ie,
	ak@suse.de, apw@shadowen.org
Subject: Re: x86_64: Make sparsemem/vmemmap the default memory model
Date: Thu, 15 Nov 2007 14:12:12 -0800	[thread overview]
Message-ID: <20071115141212.acb215f1.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711121940410.30269@schroedinger.engr.sgi.com>

On Mon, 12 Nov 2007 19:42:31 -0800 (PST)
Christoph Lameter <clameter@sgi.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, 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>

  parent reply	other threads:[~2007-11-15 22:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 23:52 x86_64: Make sparsemem/vmemmap the default memory model Christoph Lameter
2007-11-12 23:52 ` Christoph Lameter
2007-11-12 23:59 ` Andi Kleen
2007-11-12 23:59   ` Andi Kleen
2007-11-13  0:42   ` Christoph Lameter
2007-11-13  0:42     ` Christoph Lameter
2007-11-13  0:49     ` Andi Kleen
2007-11-13  0:49       ` Andi Kleen
2007-11-13  3:42       ` Christoph Lameter
2007-11-13  3:42         ` Christoph Lameter
2007-11-13  4:27         ` Ray Lee
2007-11-13  4:27           ` Ray Lee
2007-11-13  4:41           ` Christoph Lameter
2007-11-13  4:41             ` Christoph Lameter
2007-11-13 20:41             ` Jörn Engel
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-13 22:30                   ` Jörn Engel
2007-11-15 22:12         ` Andrew Morton [this message]
2007-11-15 22:12           ` Andrew Morton
2007-11-16  2:24           ` Christoph Lameter
2007-11-16  2:24             ` Christoph Lameter
2007-11-16  2:52             ` Andrew Morton
2007-11-16  2:52               ` Andrew Morton
2007-11-16  3:55               ` x86_64: Make sparsemem/vmemmap the default memory model V2 Christoph Lameter
2007-11-16  3:55                 ` 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=20071115141212.acb215f1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ak@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.