[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170530150504.tks7tg45ucosxrjg@arbab-laptop.localdomain>
Date: Tue, 30 May 2017 10:05:04 -0500
From: Reza Arbab <arbab@...ux.vnet.ibm.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
Mel Gorman <mgorman@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Andrea Arcangeli <aarcange@...hat.com>,
Jerome Glisse <jglisse@...hat.com>,
Yasuaki Ishimatsu <yasu.isimatu@...il.com>,
qiuxishi@...wei.com, Kani Toshimitsu <toshi.kani@....com>,
slaoub@...il.com, Joonsoo Kim <js1304@...il.com>,
Andi Kleen <ak@...ux.intel.com>,
David Rientjes <rientjes@...gle.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
Igor Mammedov <imammedo@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH 3/3] mm, memory_hotplug: move movable_node to the hotplug
proper
On Mon, May 29, 2017 at 01:41:41PM +0200, Michal Hocko wrote:
>movable_node_is_enabled is defined in memblock proper while it
>is initialized from the memory hotplug proper. This is quite messy
>and it makes a dependency between the two so move movable_node along
>with the helper functions to memory_hotplug.
>
>To make it more entertaining the kernel parameter is ignored unless
>CONFIG_HAVE_MEMBLOCK_NODE_MAP=y because we do not have the node
>information for each memblock otherwise. So let's warn when the option
>is disabled.
Acked-by: Reza Arbab <arbab@...ux.vnet.ibm.com>
--
Reza Arbab
Powered by blists - more mailing lists