From: Mel Gorman <mel@csn.ul.ie>
To: Ingo Molnar <mingo@elte.hu>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
apw@shadowen.org
Subject: Re: [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86
Date: Mon, 21 Jan 2008 16:27:02 +0000 [thread overview]
Message-ID: <20080121162702.GB8485@csn.ul.ie> (raw)
In-Reply-To: <20080121144923.GA8959@elte.hu>
On (21/01/08 15:49), Ingo Molnar didst pronounce:
>
> * Mel Gorman <mel@csn.ul.ie> wrote:
>
> > > I think this patch become easy to the porting of fakenuma.
> >
> > It would be great if that was available, particularly if it could fake
> > memoryless nodes as that is a place where we've found a few
> > difficult-to-reproduce bugs.
>
> yeah. Your previous patch (see below) had build problems - are those
> resolved meanwhile?
>
Odd, I couldn't reproduce it Friday and could today. Clearly I was not
firing on all cylinders. The problem was because NUMA && FLATMEM are
incompatible. Thanks for nudging a second time.
However in the patch below addressing the problem below, would it make more
sense to replace X86_PC with !NUMA instead of having X86_PC && !NUMA?
===
Subject: Do not allow FLATMEM && NUMA to be set on x86 at the same time
The FLATMEM memory model references a global mem_map and max_mapnr. This
is incompatible with how memory models used for NUMA view the world.
Builds fail if FLATMEM && NUMA are set on x86. This patch forbids that
combination of config items. This is consistent with x86_64
enforcements.
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-020_init_kmem3lists_nodes/arch/x86/Kconfig linux-2.6.24-rc8-025_memmap_reffix/arch/x86/Kconfig
--- linux-2.6.24-rc8-020_init_kmem3lists_nodes/arch/x86/Kconfig 2008-01-19 15:26:00.000000000 +0000
+++ linux-2.6.24-rc8-025_memmap_reffix/arch/x86/Kconfig 2008-01-21 15:51:03.000000000 +0000
@@ -891,7 +891,7 @@ config HAVE_ARCH_ALLOC_REMAP
config ARCH_FLATMEM_ENABLE
def_bool y
- depends on (X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC) || (X86_64 && !NUMA)
+ depends on (X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA) || (X86_64 && !NUMA)
config ARCH_DISCONTIGMEM_ENABLE
def_bool y
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2008-01-21 16:27 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 ` [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set " Mel Gorman
2008-01-18 16:17 ` 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 [this message]
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=20080121162702.GB8485@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=apw@shadowen.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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).