public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] x86_64 out of line numa funcs are discontig only
Date: Wed, 11 Jan 2006 19:26:42 +0000	[thread overview]
Message-ID: <43C55BF2.40500@shadowen.org> (raw)

Grrrr, patch sender collapsed the cc lines ...

-------- Original Message --------
Subject: [PATCH] x86_64 out of line numa funcs are discontig only
Date: Wed, 11 Jan 2006 18:14:11 +0000
From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@osdl.org>
CC: Andi Kleen <ak@suse.de>
References: <20060111042135.24faf878.akpm@osdl.org>

x86_64 out of line numa funcs are discontig only

The following patch included in 2.6.15-mm3 moves the inline DISCONTIGMEM
page accessor functions into numa.c.  However, these are only used under
DISCONTIGMEM and need covered by CONFIG_DISCONTIGMEM:

    x86_64-out-of-line-numa-funcs.patch

Signed-off-by: Andy Whitcroft <apw@shadowen.org>
---
 numa.c |    2 ++
 1 files changed, 2 insertions(+)
diff -upN reference/arch/x86_64/mm/numa.c current/arch/x86_64/mm/numa.c
--- reference/arch/x86_64/mm/numa.c
+++ current/arch/x86_64/mm/numa.c
@@ -361,6 +361,7 @@ EXPORT_SYMBOL(memnode_shift);
 EXPORT_SYMBOL(memnodemap);
 EXPORT_SYMBOL(node_data);

+#ifdef CONFIG_DISCONTIGMEM
 /*
  * Functions to convert PFNs from/to per node page addresses.
  * These are out of line because they are quite big.
@@ -394,3 +395,4 @@ int pfn_valid(unsigned long pfn)
 	return pfn >= node_start_pfn(nid) && (pfn) < node_end_pfn(nid);
 }
 EXPORT_SYMBOL(pfn_valid);
+#endif /* CONFIG_DISCONTIGMEM */

                 reply	other threads:[~2006-01-11 19:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43C55BF2.40500@shadowen.org \
    --to=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.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