From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.0-test3: #undef SMP && #define NUMA does not compile
Date: Mon, 18 Aug 2003 16:00:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106122249828930@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106122187228169@msgid-missing>
On Mon, Aug 18, 2003 at 05:46:17PM +0200, Andreas Schwab wrote:
> When configuring 2.6.0-test3 with CONFIG_SMP disabled and CONFIG_NUMA
> enabled I get undefined references to cpu_to_node_map and
> node_to_cpu_mask. Both variables are defined in
> arch/ia64/kernel/smpboot.c, thus only available for SMP.
Surely we should make NUMA depend on SMP? Or does someone have an
example of a NUMA single-processor box ;-)
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-08-18 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 15:46 2.6.0-test3: #undef SMP && #define NUMA does not compile Andreas Schwab
2003-08-18 16:00 ` Matthew Wilcox [this message]
2003-08-18 16:05 ` Andreas Schwab
2003-08-18 16:13 ` Matthew Wilcox
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=marc-linux-ia64-106122249828930@msgid-missing \
--to=willy@debian.org \
--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