From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Sonny Rao <sonny@burdell.org>, Paul Mackerras <paulus@samba.org>
Cc: torvalds@osdl.org, akpm@osdl.org, anton@samba.org,
Mike Kravetz <kravetz@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] POWER 4 fails to boot with NUMA
Date: Tue, 02 Aug 2005 08:43:50 -0700 [thread overview]
Message-ID: <1980000.1122997430@[10.10.2.4]> (raw)
In-Reply-To: <20050801062322.GA32415@kevlar.burdell.org>
--Sonny Rao <sonny@burdell.org> wrote (on Monday, August 01, 2005 02:23:22 -0400):
> On Mon, Aug 01, 2005 at 12:27:42AM -0500, Paul Mackerras wrote:
>> From: Mike Kravetz <kravetz@us.ibm.com>
>>
>> If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is
>> because of special processing needed to handle invalid node IDs (0xffff)
>> on POWER 4. My previous patch to handle memory 'holes' within nodes
>> forgot to add this special case for POWER 4 in one place.
>>
>> In reality, I'm not sure that configuring the kernel for NUMA on POWER 4
>> makes much sense. Are there POWER 4 based systems with NUMA characteristics
>> that are presented by the firmware? But, distros want one kernel for all
>> systems so NUMA is on by default in their kernels. The patch handles those
>> cases.
>
> IIRC, In SMP mode the NUMA topology is exported. I've tried this on a
> p690 and it worked correctly on older kernels (2.6.10 or 2.6.11)
>
> I also noticed a nice speedup on a few things compared to LPAR mode :-)
Yeah, I have a p650 that's set up similarly .... I thought the auto-test
stuff was covering that, but it seems NUMA is not turned on for that box
like I thought it was. will fix ....
M.
prev parent reply other threads:[~2005-08-02 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 5:27 Paul Mackerras
2005-08-01 6:23 ` Sonny Rao
2005-08-02 15:43 ` Martin J. Bligh [this message]
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='1980000.1122997430@[10.10.2.4]' \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sonny@burdell.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®