From: Mel Gorman <mel@csn.ul.ie>
To: mingo@elte.hu
Cc: linux-mm@kvack.org, apw@shadowen.org,
linux-kernel@vger.kernel.org, Mel Gorman <mel@csn.ul.ie>
Subject: [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set CONFIG_NUMA on x86
Date: Fri, 18 Jan 2008 15:35:49 +0000 (GMT) [thread overview]
Message-ID: <20080118153549.12646.1915.sendpatchset@skynet.skynet.ie> (raw)
In-Reply-To: <20080118153529.12646.5260.sendpatchset@skynet.skynet.ie>
There is nothing inherent in HIGHMEM64G required for CONFIG_NUMA to work. It
just limits potential testing coverage so remove the limitation.
Signed-off-by: Mel Gorman <mel@csn.ul.ie>
---
arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff linux-2.6.24-rc8-fix-numa-boot/arch/x86/Kconfig linux-2.6.24-rc8-005_non64GB/arch/x86/Kconfig
--- linux-2.6.24-rc8-fix-numa-boot/arch/x86/Kconfig 2008-01-16 04:22:48.000000000 +0000
+++ linux-2.6.24-rc8-005_non64GB/arch/x86/Kconfig 2008-01-17 18:22:26.000000000 +0000
@@ -817,7 +817,7 @@ config X86_PAE
config NUMA
bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
depends on SMP
- depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
+ depends on X86_64 || (X86_32 && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
default n if X86_PC
default y if (X86_NUMAQ || X86_SUMMIT)
help
--
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>
next prev parent reply other threads:[~2008-01-18 15:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 15:35 [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 Mel Gorman
2008-01-18 15:35 ` Mel Gorman [this message]
2008-01-18 16:17 ` [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set " Ingo Molnar
2008-01-18 15:36 ` [PATCH 2/2] Allow any x86 sub-architecture type to set CONFIG_NUMA Mel Gorman
2008-01-18 16:17 ` Ingo Molnar
2008-01-19 6:35 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 Andi Kleen
2008-01-19 16:07 ` Mel Gorman
2008-01-22 12:14 ` Ingo Molnar
2008-01-22 12:29 ` Mel Gorman
2008-01-22 15:39 ` Ingo Molnar
2008-01-22 13:33 ` Andi Kleen
2008-01-23 10:28 ` Mel Gorman
2008-01-23 10:45 ` Andi Kleen
2008-01-23 10:57 ` Mel Gorman
2008-01-23 11:11 ` Andi Kleen
2008-01-23 11:15 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 II Andi Kleen
2008-01-23 11:24 ` Mel Gorman
2008-01-23 13:48 ` Andi Kleen
2008-01-23 14:15 ` Mel Gorman
2008-01-21 0:38 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 KOSAKI Motohiro
2008-01-21 14:35 ` Mel Gorman
2008-01-21 14:49 ` Ingo Molnar
2008-01-21 16:27 ` Mel Gorman
2008-01-23 2:04 ` KOSAKI Motohiro
2008-01-23 10:22 ` Mel Gorman
2008-01-24 3:19 ` KOSAKI Motohiro
2008-01-23 10:23 ` Mel Gorman
2008-01-26 14:10 ` KOSAKI Motohiro
2008-01-26 17:10 ` KOSAKI Motohiro
2008-01-26 17:18 ` Mel Gorman
2008-01-27 6:54 ` KOSAKI Motohiro
2008-01-28 15:02 ` Ingo Molnar
2008-01-29 2:57 ` KOSAKI Motohiro
2008-01-29 11:34 ` Mel Gorman
2008-02-03 9:32 ` KOSAKI Motohiro
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=20080118153549.12646.1915.sendpatchset@skynet.skynet.ie \
--to=mel@csn.ul.ie \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).