From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: NODE_DATA without CONFIG_NUMA
Date: Mon, 04 Sep 2006 06:23:25 +0000 [thread overview]
Message-ID: <20060904062323.GA9293@verge.net.au> (raw)
Hi,
I'm trying to build a non-NUMA (HP_SIM) config, and I am running
into trouble because there are serveral places where NODE_DATA is
used. It seems to me that this makes little sense as NODE_DATA
needs the node_data element of struct cpuinfo_ia64, which doesn't
exist without CONFIG_NUMA.
Is CONFIG_NUMA mandatory or is this just an oversight?
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
--
VGER BF report: U 0.500823
next reply other threads:[~2006-09-04 6:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 6:23 Horms [this message]
2006-09-04 6:37 ` NODE_DATA without CONFIG_NUMA KAMEZAWA Hiroyuki
2006-09-04 7:06 ` Horms
2006-09-04 7:43 ` Jes Sorensen
2006-09-04 7:45 ` KAMEZAWA Hiroyuki
2006-09-04 7:56 ` Horms
2006-09-04 8:05 ` Jes Sorensen
2006-09-04 8:22 ` Horms
2006-09-04 8:55 ` Jes Sorensen
2006-09-04 16:15 ` Christoph Lameter
2006-09-04 17:15 ` Jes Sorensen
2006-09-04 17:39 ` Christoph Lameter
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=20060904062323.GA9293@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.