[lkml]   [2019]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
SubjectRe: [PATCH 3/5] x86: Kconfig: Remove CONFIG_NODES_SPAN_OTHER_NODES

On Tue, 25 Jun 2019, Hoan Tran OS wrote:

Please use 'x86/Kconfig: ' as prefix.

> This patch removes CONFIG_NODES_SPAN_OTHER_NODES as it's
> enabled by default with NUMA.

Please do not use 'This patch' in changelogs. It's pointless because we
already know that this is a patch.

See also Documentation/process/submitting-patches.rst and search for 'This

Simply say:

Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled by default with

But .....

> @@ -1567,15 +1567,6 @@ config X86_64_ACPI_NUMA
> ---help---
> Enable ACPI SRAT based node topology detection.
> -# Some NUMA nodes have memory ranges that span
> -# other nodes. Even though a pfn is valid and
> -# between a node's start and end pfns, it may not
> -# reside on that node. See memmap_init_zone()
> -# for details.
> - def_bool y
> - depends on X86_64_ACPI_NUMA

the changelog does not mention that this lifts the dependency on
X86_64_ACPI_NUMA and therefore enables that functionality for anything
which has NUMA enabled including 32bit.

The core mm change gives no helpful information either. You just copied the
above comment text from some random Kconfig.

This needs a bit more data in the changelogs and the cover letter:

- Why is it useful to enable it unconditionally

- Why is it safe to do so, even if the architecture had constraints on

- What's the potential impact



 \ /
  Last update: 2019-06-26 00:47    [W:0.077 / U:3.952 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site