From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f199.google.com (mail-wr0-f199.google.com [209.85.128.199]) by kanga.kvack.org (Postfix) with ESMTP id 4F4C36B0493 for ; Mon, 10 Jul 2017 08:12:59 -0400 (EDT) Received: by mail-wr0-f199.google.com with SMTP id z81so23770078wrc.2 for ; Mon, 10 Jul 2017 05:12:59 -0700 (PDT) Received: from mx1.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id u27si7885379wru.142.2017.07.10.05.12.57 for (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 10 Jul 2017 05:12:58 -0700 (PDT) Subject: Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions References: <20170629073509.623-1-mhocko@kernel.org> <20170629073509.623-3-mhocko@kernel.org> <64e889ae-24ab-b845-5751-978a76dd0dd9@suse.cz> <20170710064540.GA19185@dhcp22.suse.cz> <24c3606d-837a-266d-a294-7e100d1430f0@suse.cz> <20170710111750.GG19185@dhcp22.suse.cz> From: Vlastimil Babka Message-ID: Date: Mon, 10 Jul 2017 14:12:09 +0200 MIME-Version: 1.0 In-Reply-To: <20170710111750.GG19185@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: linux-mm@kvack.org, Andrew Morton , Mel Gorman , Andrea Arcangeli , Reza Arbab , Yasuaki Ishimatsu , qiuxishi@huawei.com, Kani Toshimitsu , slaoub@gmail.com, Joonsoo Kim , Daniel Kiper , Igor Mammedov , Vitaly Kuznetsov , Wei Yang , LKML , Linux API On 07/10/2017 01:17 PM, Michal Hocko wrote: > On Mon 10-07-17 13:11:29, Vlastimil Babka wrote: >> On 07/10/2017 08:45 AM, Michal Hocko wrote: >>> On Fri 07-07-17 17:02:59, Vlastimil Babka wrote: >>>> [+CC linux-api] >>>> >>>> >>>> Hm so previously, blocks 37-41 would only allow Movable at this point, right? >>> >>> yes >>> >>>> Shouldn't we still default to Movable for them? We might be breaking some >>>> existing userspace here. >>> >>> I do not think so. Prior to this merge window f1dd2cd13c4b ("mm, >>> memory_hotplug: do not associate hotadded memory to zones until online") >>> we allowed only the last offline or the adjacent to existing movable >>> memory block to be onlined movable. So the above wasn't possible. >> >> Not exactly the above, but let's say 1-34 is onlined as Normal, 35-37 is >> Movable. Then the only possible action before would be online 38 as >> Movable? Now it defaults to Normal? > > Yes. And let me repeat you couldn't onlne 35-37 as movable before. So no > userspace could depend on that before the rework. Or do I still miss > your point? Ah, I see. "the last offline or the adjacent to existing movable". OK then. It would be indeed better to not change behavour twice then and merge this to 4.13, but it's the middle of merge window, so it's not simple... -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org