From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752276AbbHTHol (ORCPT ); Thu, 20 Aug 2015 03:44:41 -0400 Received: from mx2.suse.de ([195.135.220.15]:39580 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751284AbbHTHok (ORCPT ); Thu, 20 Aug 2015 03:44:40 -0400 Subject: Re: [PATCH V2] mm:memory hot-add: memory can not been added to movable zone To: Changsheng Liu , akpm@linux-foundation.org, isimatu.yasuaki@jp.fujitsu.com References: <1440055685-6083-1-git-send-email-liuchangsheng@inspur.com> <55D584C7.7060101@suse.cz> Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, yanxiaofeng@inspur.com, fandd@inspur.com, Changsheng Liu From: Vlastimil Babka Message-ID: <55D58566.4040709@suse.cz> Date: Thu, 20 Aug 2015 09:44:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <55D584C7.7060101@suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/20/2015 09:41 AM, Vlastimil Babka wrote: > want to hot-remove and don't want movable zones (which limit what kind > of allocations are possible), is there a way to prevent memory being > movable after your patch? Oh, and not enabling CONFIG_MOVABLE_NODE is not sufficient here IMHO, as users might want to use a distro kernel that has the option enabled, but still not want to use it.