Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1652463
| From | Vlastimil Babka <vbabka@suse.cz> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE |
| Date | 2017-05-29 14:10 +0200 |
| Message-ID | <tMrEJ-865-1@gated-at.bofh.it> (permalink) |
| References | <tMrln-7Ii-5@gated-at.bofh.it> <tMrln-7Ii-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 05/29/2017 01:41 PM, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> 20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated
> node") has introduced CONFIG_MOVABLE_NODE without a good explanation on
> why it is actually useful. It makes a lot of sense to make movable node
> semantic opt in but we already have that because the feature has to be
> explicitly enabled on the kernel command line. A config option on top
> only makes the configuration space larger without a good reason. It also
> adds an additional ifdefery that pollutes the code. Just drop the config
> option and make it de-facto always enabled. This shouldn't introduce any
> change to the semantic.
>
> Acked-by: Reza Arbab <arbab@linux.vnet.ibm.com>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE Michal Hocko <mhocko@kernel.org> - 2017-05-29 13:50 +0200 Re: [PATCH 2/3] mm, memory_hotplug: drop CONFIG_MOVABLE_NODE Vlastimil Babka <vbabka@suse.cz> - 2017-05-29 14:10 +0200
csiph-web