public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] IA64: Sparse and Discontig Mem need NUMA
Date: Wed, 02 May 2007 08:27:19 +0000	[thread overview]
Message-ID: <20070502082716.GA6689@verge.net.au> (raw)

It was pointed out to me by my colleague Yamahata-san that
neither sparse nor discontig mem compile without NUMA support.

Cc: Alex Williamson <alex.williamson@hp.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>
Signed-off-by: Simon Horman <horms@verge.net.au>

--- 
This seems line an issue best solved by prohibiting such settings through
Kconfig. But if it is desirable for sparse and discontig memory to work
without CONFIG_NUMA let me know and I'll have a stab at it. It does seem
possible code-wise. I'm just not sure if its useful.

Index: linux-2.6/arch/ia64/Kconfig
=================================--- linux-2.6.orig/arch/ia64/Kconfig	2007-05-02 16:42:22.000000000 +0900
+++ linux-2.6/arch/ia64/Kconfig	2007-05-02 16:42:26.000000000 +0900
@@ -337,6 +337,7 @@ config ARCH_SELECT_MEMORY_MODEL
 
 config ARCH_DISCONTIGMEM_ENABLE
 	def_bool y
+	depends on NUMA
 	help
 	  Say Y to support efficient handling of discontiguous physical memory,
 	  for architectures which are either NUMA (Non-Uniform Memory Access)
@@ -345,6 +346,7 @@ config ARCH_DISCONTIGMEM_ENABLE
 
 config ARCH_FLATMEM_ENABLE
 	def_bool y
+	depends on !NUMA
 
 config ARCH_SPARSEMEM_ENABLE
 	def_bool y
@@ -356,7 +358,7 @@ config ARCH_DISCONTIGMEM_DEFAULT
 
 config NUMA
 	bool "NUMA support"
-	depends on !IA64_HP_SIM && !FLATMEM
+	depends on !IA64_HP_SIM
 	default y if IA64_SGI_SN2
 	select ACPI_NUMA if ACPI
 	help

             reply	other threads:[~2007-05-02  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  8:27 Simon Horman [this message]
2007-05-02 16:22 ` [PATCH] IA64: Sparse and Discontig Mem need NUMA Luck, Tony
2007-05-03  1:26 ` Simon Horman

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=20070502082716.GA6689@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-ia64@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