mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, Ravikiran G Thirumalai <kiran@scalex86.org>,
	linux-kernel@vger.kernel.org,
	"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>
Subject: Re: [discuss] [rfc] x86_64: Kconfig changes for NUMA
Date: Thu, 27 Oct 2005 10:40:37 +0900	[thread overview]
Message-ID: <aec7e5c30510261840xf0d5bfapaf2f62959cb9a462@mail.gmail.com> (raw)
In-Reply-To: <200510261646.26331.ak@suse.de>

On 10/26/05, Andi Kleen <ak@suse.de> wrote:
> On Wednesday 26 October 2005 09:09, Ravikiran G Thirumalai wrote:
>
> >
> > 1. Makes NUMA a config option like other arches
> > 2. Makes topology detection options like K8_NUMA dependent on NUMA
> > 3. Choosing ACPI NUMA detection can be done from the standard
> >    "Processor type and features" menu
> > Comments?
>
> It's in principle ok except that I don't like the dependencies and
> defaults. K8_NUMA shouldn't be dependent on !M_PSC. And the defaults
> should be just dropped.

While at it, could you please consider to remove the SMP dependency
from NUMA_EMU? 2.6.14-rc5-git5 builds and works with !SMP and
NUMA_EMU.

Why?
1. No need to force SMP when not needed.
2. qemu-system-x86_64 does not currently work with SMP kernels.

Thanks,

/ magnus

  parent reply	other threads:[~2005-10-27  1:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26  7:09 Ravikiran G Thirumalai
2005-10-26 14:46 ` [discuss] " Andi Kleen
2005-10-26 20:20   ` Ravikiran G Thirumalai
2005-10-26 21:39     ` Andi Kleen
2005-10-27  1:40   ` Magnus Damm [this message]
2005-10-27  6:25     ` Magnus Damm
2005-10-27  7:50       ` Andi Kleen
2005-10-27  8:25         ` Magnus Damm
2005-10-27  8:31           ` 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=aec7e5c30510261840xf0d5bfapaf2f62959cb9a462@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shai@scalex86.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®