linux-kernel - Re: [PATCH V2] mm:memory hot-add: memory can not been added to movable zone

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55D58566.4040709@suse.cz>
Date:	Thu, 20 Aug 2015 09:44:38 +0200
From:	Vlastimil Babka <vbabka@...e.cz>
To:	Changsheng Liu <liuchangsheng@...pur.com>,
	akpm@...ux-foundation.org, isimatu.yasuaki@...fujitsu.com
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	yanxiaofeng@...pur.com, fandd@...pur.com,
	Changsheng Liu <liuchangcheng@...pur.com>
Subject: Re: [PATCH V2] mm:memory hot-add: memory can not been added to
 movable zone

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/