From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D1B77C4360F for ; Mon, 1 Apr 2019 07:59:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ACA71213A2 for ; Mon, 1 Apr 2019 07:59:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732199AbfDAH7i (ORCPT ); Mon, 1 Apr 2019 03:59:38 -0400 Received: from charybdis-ext.suse.de ([195.135.221.2]:44522 "EHLO suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1731944AbfDAH7i (ORCPT ); Mon, 1 Apr 2019 03:59:38 -0400 Received: by suse.de (Postfix, from userid 1000) id CF946479F; Mon, 1 Apr 2019 09:59:36 +0200 (CEST) Date: Mon, 1 Apr 2019 09:59:36 +0200 From: Oscar Salvador To: Michal Hocko Cc: David Hildenbrand , akpm@linux-foundation.org, dan.j.williams@intel.com, Jonathan.Cameron@huawei.com, anshuman.khandual@arm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 0/4] mm,memory_hotplug: allocate memmap from hotadded memory Message-ID: <20190401075936.bjt2qsrhw77rib77@d104.suse.de> References: <20190328134320.13232-1-osalvador@suse.de> <20190329084547.5k37xjwvkgffwajo@d104.suse.de> <20190329134243.GA30026@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190329134243.GA30026@dhcp22.suse.cz> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 29, 2019 at 02:42:43PM +0100, Michal Hocko wrote: > Having a larger contiguous area is definitely nice to have but you also > have to consider the other side of the thing. If we have a movable > memblock with unmovable memory then we are breaking the movable > property. So there should be some flexibility for caller to tell whether > to allocate on per device or per memblock. Or we need something to move > memmaps during the hotremove. By movable memblock you mean a memblock whose pages can be migrated over when this memblock is offlined, right? -- Oscar Salvador SUSE L3