From: Christoph Hellwig <hch@infradead.org>
To: Patricia Gaughen <gone@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] discontigmem support for ia32 NUMA box against 2.4.19pre7
Date: Tue, 30 Apr 2002 07:26:54 +0100 [thread overview]
Message-ID: <20020430072654.B2262@infradead.org> (raw)
In-Reply-To: <200204300115.g3U1FQc16634@w-gaughen.des.beaverton.ibm.com>
On Mon, Apr 29, 2002 at 06:15:26PM -0700, Patricia Gaughen wrote:
> + if [ "$CONFIG_MULTIQUAD" = "y" ]; then
> + bool 'Discontiguous Memory Support' CONFIG_DISCONTIGMEM
> + if [ "$CONFIG_DISCONTIGMEM" = "y" ]; then
> + define_bool CONFIG_DISCONTIGMEM_X86 y
> + define_bool CONFIG_IBMNUMAQ y
> + define_bool CONFIG_NUMA y
> + fi
> + fi
CML code uses three tab indentes. Also the way you do the config looks
rather strange. I'd rather ask for IBM NUMAQ support and imply NUMA &
DISCONTIGMEM support if set. Also CONFIG_DISCONTIGMEM_X86 looks like
an ugly workaround to me, all places where it is used should rather check
for one of CONFIG_DISCONTIGMEM/CONFIG_NUMA/CONFIG_IBMNUMAQ.
(and CONFIG_IBMNUMAQ would better be named CONFIG_X86_NUMAQ, IMHO).
> +
> +#ifdef CONFIG_SMP
> + /*
> + * But first pinch a few for the stack/trampoline stuff
> + * FIXME: Don't need the extra page at 4K, but need to fix
> + * trampoline before removing it. (see the GDT stuff)
> + */
> + reserve_bootmem_node(NODE_DATA(0), PAGE_SIZE, PAGE_SIZE);
> +#endif
Umm, NUMA without SMP looks rather strange to me..
> +#ifdef CONFIG_X86_LOCAL_APIC
> + /*
> + * Find and reserve possible boot-time SMP configuration:
> + */
> + find_smp_config();
> +#endif
Dito for local APIC.
next prev parent reply other threads:[~2002-04-30 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 1:15 [RFC] discontigmem support for ia32 NUMA box against 2.4.19pre7 Patricia Gaughen
2002-04-30 6:26 ` Christoph Hellwig [this message]
2002-05-01 0:56 ` Patricia Gaughen
2002-05-01 5:48 ` Martin J. Bligh
2002-05-01 1:22 ` William Lee Irwin III
2002-05-01 9:23 ` Christoph Hellwig
2002-05-01 18:00 ` Patricia Gaughen
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=20020430072654.B2262@infradead.org \
--to=hch@infradead.org \
--cc=gone@us.ibm.com \
--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