From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: NODE_DATA without CONFIG_NUMA
Date: Mon, 04 Sep 2006 07:43:35 +0000 [thread overview]
Message-ID: <yq0ac5ghyag.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20060904062323.GA9293@verge.net.au>
>>>>> "Horms" = Horms <horms@verge.net.au> writes:
Horms> Hi, I'm trying to build a non-NUMA (HP_SIM) config, and I am
Horms> running into trouble because there are serveral places where
Horms> NODE_DATA is used. It seems to me that this makes little sense
Horms> as NODE_DATA needs the node_data element of struct
Horms> cpuinfo_ia64, which doesn't exist without CONFIG_NUMA.
Horms> Is CONFIG_NUMA mandatory or is this just an oversight?
I haven't looked at the details, given you don't say where it breaks,
but it would make sense to me that a non-NUMA system is treated as a
single node system, eg. NODE_DATA(0) ought to be valid.
Cheers,
Jes
--
VGER BF report: U 0.501786
next prev parent reply other threads:[~2006-09-04 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 6:23 NODE_DATA without CONFIG_NUMA Horms
2006-09-04 6:37 ` KAMEZAWA Hiroyuki
2006-09-04 7:06 ` Horms
2006-09-04 7:43 ` Jes Sorensen [this message]
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=yq0ac5ghyag.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--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