linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Andy Whitcroft <apw@shadowen.org>,
	kravetz@us.ibm.com, anton@samba.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/2] SPARSEMEM: pfn_to_nid implementation v2
Date: Tue, 22 Nov 2005 18:07:24 +0000	[thread overview]
Message-ID: <exportbomb.1132682844@pinky> (raw)
In-Reply-To: <20051119233151.01ce6c50.akpm@osdl.org>

There are three places we define pfn_to_nid().  Two in linux/mmzone.h
and one in asm/mmzone.h.  These in essence represent the three memory
models.  The definition in linux/mmzone.h under !NEED_MULTIPLE_NODES
is both the FLATMEM definition and the optimisation for single
NUMA nodes; the one under SPARSEMEM is the NUMA sparsemem one;
the one in asm/mmzone.h under DISCONTIGMEM is the discontigmem one.
This is not in the least bit obvious, particularly the connection
between the non-NUMA optimisations and the memory models.

Following in the email are two patches:

flatmem-split-out-memory-model: simplifies the selection of
    pfn_to_nid() implementations.  The selection is based primarily
    off the memory model selected.  Optimisations for non-NUMA are
    applied where needed.

sparse-provide-pfn_to_nid: implement pfn_to_nid() for SPARSEMEM

Boot tested on for both SPARSEMEM and DISCONTIGMEM on all my test
boxes.  Also compile tested for FLATMEM and SPARSEMEM without NUMA.
Against 2.6.15-rc2.

Next I'll review the configuration options to see if we can simplify
them any.

-apw

--
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:[~2005-11-22 18:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 22:10 pfn_to_nid under CONFIG_SPARSEMEM and CONFIG_NUMA Mike Kravetz
2005-11-16  3:14 ` Yasunori Goto
2005-11-16 13:00   ` Robin Holt
2005-11-16 13:25 ` Andy Whitcroft
2005-11-16 22:59 ` [PATCH 0/3] SPARSEMEM: pfn_to_nid implementation Andy Whitcroft
2005-11-16 23:00   ` [PATCH 1/3] kvaddr_to_nid not used in common code Andy Whitcroft
2005-11-16 23:00   ` [PATCH 2/3] pfn_to_pgdat " Andy Whitcroft
2005-11-16 23:00   ` [PATCH 3/3] sparse provide pfn_to_nid Andy Whitcroft
2005-11-20  7:31     ` Andrew Morton
2005-11-20 12:21       ` Andy Whitcroft
2005-11-22 18:07       ` Andy Whitcroft [this message]
2005-11-22 18:07         ` [PATCH 1/2] flatmem split out memory model Andy Whitcroft
2005-11-22 18:07         ` [PATCH 2/2] sparse provide pfn_to_nid Andy Whitcroft
2005-11-17  0:06   ` [PATCH 0/3] SPARSEMEM: pfn_to_nid implementation Mike Kravetz

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=exportbomb.1132682844@pinky \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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