From: Andi Kleen <ak@suse.de>
To: "Keith Mannthey" <kmannth@gmail.com>
Cc: "Dave Jones" <davej@redhat.com>,
torvalds@osdl.org, discuss@x86-64.org, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [20/82] i386: Panic the system when a NUMA kernel doesn't run on IBM NUMA
Date: Sat, 24 Jun 2006 03:15:56 +0200 [thread overview]
Message-ID: <200606240315.56365.ak@suse.de> (raw)
In-Reply-To: <a762e240606231803p72e4e684v42cf27cdaf8fb30f@mail.gmail.com>
>
> I agree that i386 CONFIG_NUMA is only ment to boot on small subset of
> hw but there is litte motivation to boot a numa kernel on a non-numa
> box. I am supprised that no one has enabled i386 AMD NUMA (the one
> numa box that regular people have access to).
I never bothered because 32bit NUMA with lowmem only on node 0
isn't very useful. Using it with 64bit makes much more sense.
> > I'm sure someone will bring up now an example where their non Summit
> > machine booted with CONFIG_NUMA, but they were just extremly lucky
> > and unlikely to be for very long.
>
> Current Summit HW (x460) dosen't use/have a cyclone. There are
> patches submitted to this list to support it's i386 NUMA boot.
Hmm, that's a good point. When the detection doesn't work
reliable it's no good.
Ok, Linus please don't apply that patch for now then.
-Andi
prev parent reply other threads:[~2006-06-24 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 0:19 [PATCH] [20/82] i386: Panic the system when a NUMA kernel doesn't run on IBM NUMA Andi Kleen
2006-06-24 0:38 ` Dave Jones
2006-06-24 0:42 ` Andi Kleen
2006-06-24 1:03 ` Keith Mannthey
2006-06-24 1:15 ` Andi Kleen [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=200606240315.56365.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=discuss@x86-64.org \
--cc=kmannth@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.