mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Fix CONFIG_NUMA help message
Date: Sat, 26 Sep 2009 21:44:58 +0200	[thread overview]
Message-ID: <4ABE6F3A.9000901@ens-lyon.org> (raw)
In-Reply-To: <20090926181837.GA15018@basil.fritz.box>

Andi Kleen wrote:
> Noticed recently while looking at this file. The x86 NUMA Kconfig help
> entry is not quite correct.
>
> - Core i7 systems are always non NUMA. Refer to multi socket Nehalems instead.
> - Replace outdated EM64T term with Intel 64
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
>  arch/x86/Kconfig |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 384a897..47c81bd 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1118,8 +1118,9 @@ config NUMA
>  	  local memory controller of the CPU and add some more
>  	  NUMA awareness to the kernel.
>  
> -	  For 64-bit this is recommended if the system is Intel Core i7
> -	  (or later), AMD Opteron, or EM64T NUMA.
> +	  For 64-bit this is recommended if the system is Intel Xeon 75xx
> +	  (Intel Nehalem based multi socket systems), AMD Opteron, or Intel
> +          64 NUMA.
>  
>  	  For 32-bit this is only needed on (rare) 32-bit-only platforms
>  	  that support NUMA topologies, such as NUMAQ / Summit, or if you
>   

Why Xeon 75xx and not 55xx ?

Brice


      reply	other threads:[~2009-09-26 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 18:18 Andi Kleen
2009-09-26 19:44 ` Brice Goglin [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=4ABE6F3A.9000901@ens-lyon.org \
    --to=brice.goglin@ens-lyon.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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

all inboxes | Powered by JetHome®