LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Chris Snook <csnook@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] change CONFIG_NUMA description
Date: Thu, 06 Nov 2008 23:51:28 +0100 [thread overview]
Message-ID: <87bpwso4cv.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4910A43B.5030908@redhat.com> (Chris Snook's message of "Tue, 04 Nov 2008 14:36:27 -0500")
Chris Snook <csnook@redhat.com> writes:
> KOSAKI Motohiro wrote:
>> CONFIG_NUMA description talk about a bit old thing.
>> So, following changes are better.
>> o CONFIG_NUMA is no longer EXPERIMENTAL
>> o Opteron is not the only processor of NUMA topology on x86_64 no longer, but also Intel Core7i has it.
>> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
>
> a) It's Core i7, not Core 7i
> b) Core i7 is, at least so far, the single-socket version, so NUMA
> doesn't apply.
>
> I think we should let Intel write the CONFIG_NUMA description for
> Nehalem processors.
The recommendation should be imho just to always enable it. Back
when I wrote the description it was still experimental, but
it really isn't anymore.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-11-06 22:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 17:27 KOSAKI Motohiro
2008-11-04 19:36 ` Chris Snook
2008-11-06 22:51 ` Andi Kleen [this message]
2008-11-04 20:11 ` Pekka Enberg
2008-11-06 8:53 ` Ingo Molnar
2008-11-06 10:15 ` Pekka Enberg
2008-11-06 10:18 ` KOSAKI Motohiro
2008-11-06 10:22 ` Ingo Molnar
2008-11-07 22:13 ` Chris Snook
2008-11-08 12:31 ` Ingo Molnar
2008-11-09 11:41 ` KOSAKI Motohiro
2008-11-06 22:50 ` Andi Kleen
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=87bpwso4cv.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=csnook@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] change CONFIG_NUMA description' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).