public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org, Russ Anderson <rja@sgi.com>
Subject: Re: [2.6 patch] ia64: let NUMA select SMP
Date: Fri, 25 Apr 2008 05:50:49 -0700	[thread overview]
Message-ID: <4811D3A9.4060602@sgi.com> (raw)
In-Reply-To: <20080425004139.GE18854@cs181133002.pp.htv.fi>

Adrian Bunk wrote:
> On Thu, Apr 24, 2008 at 05:25:06PM -0700, Luck, Tony wrote:
>>>>       Build fix for CONFIG_NUMA=y && CONFIG_SMP=n
>>>> ...
>>> Why is this an allowed configuration on ia64?
>> It shows up in allnoconfig ... probably because some
>> bit of Kconfig forces NUMA=y.
> 
> allnoconfig results in CONFIG_IA64_GENERIC=y, which in turn selects NUMA.
> 
> What about the patch below instead?
> 
>> I can't imagine that it is ever a useful combination ... except to
>> find places in the code where people have:

Though highly unlikely, it is possible to have multiple memory nodes
without having multiple cpus -- at least in theory.  In this specific
case it's nonsensical because the scheduler is grouping cpus by node.

Thanks,
Mike

>>
>> #if defined(CONFIG_SMP)
>>  ...
>> #else
>>
>> #if defined(CONFIG_NUMA) // !!! SMP=n, NUMA code???
>>   ...
>> #endif
>> #endif
>>
>>
>> Which is what happened, and is being fixed, here.
> 
> If it isn't a useful combination such code makes no sense.
> 
>> -Tony
> 
> cu
> Adrian
> 
> 
> <--  snip  -->
> 
> 
> CONFIG_NUMA=y, CONFIG_SMP=n isn't a useful combination, so let NUMA 
> select SMP.
> 
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
> 
> ---
> a94d43a82a3c5a95c82b9688e5adebca6dcb7acb diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
> index cd13e13..19e8167 100644
> --- a/arch/ia64/Kconfig
> +++ b/arch/ia64/Kconfig
> @@ -387,6 +387,7 @@ config NUMA
>  	bool "NUMA support"
>  	depends on !IA64_HP_SIM && !FLATMEM
>  	default y if IA64_SGI_SN2
> +	select SMP
>  	select ACPI_NUMA if ACPI
>  	help
>  	  Say Y to compile the kernel to support NUMA (Non-Uniform Memory
> 


      parent reply	other threads:[~2008-04-25 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 23:51 [git pull] ia64 changes Luck, Tony
2008-04-25  0:16 ` Adrian Bunk
2008-04-25  0:25   ` Luck, Tony
2008-04-25  0:41     ` [2.6 patch] ia64: let NUMA select SMP Adrian Bunk
2008-04-25  1:01       ` Luck, Tony
2008-04-25 12:50       ` Mike Travis [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=4811D3A9.4060602@sgi.com \
    --to=travis@sgi.com \
    --cc=bunk@kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rja@sgi.com \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.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