Re: [PATCH] change CONFIG_NUMA description

[Pekka Enberg]

On Tue, Nov 4, 2008 at 7:27 PM, KOSAKI Motohiro
<kosaki.motohiro@xxxxxxxxxxxxxx> wrote:
> CONFIG_NUMA description talk about a bit old thing.
> So, following changes are better.
>
> o CONFIG_NUMA is no longer EXPERIMENTAL
> Index: b/arch/x86/Kconfig
> ===================================================================
> --- a/arch/x86/Kconfig  2008-11-05 01:11:24.000000000 +0900
> +++ b/arch/x86/Kconfig  2008-11-05 02:09:38.000000000 +0900
> @@ -951,7 +951,7 @@ config ARCH_PHYS_ADDR_T_64BIT
>
>  # Common NUMA Features
>  config NUMA
> -       bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
> +       bool "Numa Memory Allocation and Scheduler Support"
>        depends on SMP
>        depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)

You might want to remove the dependency to CONFIG_EXPERIMENTAL as well.

>        default n if X86_PC
> @@ -964,9 +964,8 @@ config NUMA
>
>          For 32-bit this is currently highly experimental and should be only
>          used for kernel development. It might also cause boot failures.
> -         For 64-bit this is recommended on all multiprocessor Opteron systems.
> -         If the system is EM64T, you should say N unless your system is
> -         EM64T NUMA.
> +         For 64-bit this is recommended if the system is Intel Core 7i or later or AMD Opteron.
> +         Otherwise, you should say N unless your system is EM64T NUMA.
>
>  comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
>        depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/