Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp2473489ybi; Thu, 18 Jul 2019 08:57:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqz15loNkdxM40beqFV7frDkCYUBhdHKE0nO44CDmL18fQv+YA6XWYsipjIPMUWocaAYMnON X-Received: by 2002:a63:4e58:: with SMTP id o24mr47538653pgl.366.1563465462812; Thu, 18 Jul 2019 08:57:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563465462; cv=none; d=google.com; s=arc-20160816; b=F8EYOmKMbuyjA14+HxMbUIYIBkS4bjqlU0WdFdOzinhJT/Txim2AoU33VSnVxy+rBo GMxlhSwJ3FHF+cJrO8l4fEN2QvAUdvLzUYCnfA62K8S9axf29ixG7zDHZZ+X5eWGdH9U Y5ENMrOf64c5hDNDwj3xVWmYwBxwZGBE29Oe7jQOt48accP/Ya4Qt/J1SjTsZBYXT/yE A3kqqE6cbuTL4Hwo5vEbSz+Ix9wKWHkOw/aH6j9aM2r3uiiLmuyxapZLwDpbiMLM9aO+ 8ull9acw8iawDdpTpghRWBXy2MMdv3b6bIlQG5fHF03V4uwDl/RMgu3tGiXNwOYPf8UC rmEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=SVRVJ6ku0Lh30S7upn2pQxZyI7oLhrU90aVBWDg5Wc0=; b=s1lSxbrrHhT//Bh+Ac3qNVijccT5DLNHBXZmESdgOLMgIofc0XOcF2rPN0webd243y mfjCbXckjQq5QOh19jSWY0/Y+vTv63h3wsZezOmAukTVePiYxuewL0x1FFA6usq4+sRC zHChqZ46lAynhotGSTaavLP9JJmt7s7osUY8Ix0W0JSIVMotW+jWreW7CWLDU14pe3ZB sGwV2DCiR9sV55fKT0qH5uiAG0/Oy5r5n5f27QQzdqKO7Cfyo/xiAZDlqLGhbIsiM+jM anVyeCbQEC3Pc1goPi7QmjJPFTNeCYF3nMpInRAfsFYrRBGVLrh5OZWHnWafVt4fiR28 Nmnw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g34si1520212pld.266.2019.07.18.08.57.25; Thu, 18 Jul 2019 08:57:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727780AbfGRP5H (ORCPT + 99 others); Thu, 18 Jul 2019 11:57:07 -0400 Received: from mx2.suse.de ([195.135.220.15]:34660 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726040AbfGRP5H (ORCPT ); Thu, 18 Jul 2019 11:57:07 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 438B1AF6B; Thu, 18 Jul 2019 15:57:06 +0000 (UTC) Date: Thu, 18 Jul 2019 17:57:04 +0200 From: Michal Hocko To: Leonardo Bras Cc: Oscar Salvador , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Greg Kroah-Hartman , "Rafael J. Wysocki" , Andrew Morton , Mike Rapoport , Pavel Tatashin , =?iso-8859-1?B?Suly9G1l?= Glisse , Thomas Gleixner , Pasha Tatashin , Bartlomiej Zolnierkiewicz Subject: Re: [PATCH 1/1] mm/memory_hotplug: Adds option to hot-add memory in ZONE_MOVABLE Message-ID: <20190718155704.GD30461@dhcp22.suse.cz> References: <20190718024133.3873-1-leonardo@linux.ibm.com> <1563430353.3077.1.camel@suse.de> <0e67afe465cbbdf6ec9b122f596910cae77bc734.camel@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0e67afe465cbbdf6ec9b122f596910cae77bc734.camel@linux.ibm.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 18-07-19 12:50:29, Leonardo Bras wrote: > On Thu, 2019-07-18 at 08:12 +0200, Oscar Salvador wrote: > > We do already have "movable_node" boot option, which exactly has that > > effect. > > Any hotplugged range will be placed in ZONE_MOVABLE. > Oh, I was not aware of it. > > > Why do we need yet another option to achieve the same? Was not that > > enough for your case? > Well, another use of this config could be doing this boot option a > default on any given kernel. > But in the above case I agree it would be wiser to add the code on > movable_node_is_enabled() directly, and not where I did put. > > What do you think about it? No further config options please. We do have means a more flexible way to achieve movable node onlining so let's use it. Or could you be more specific about cases which cannot use the command line option and really need a config option to workaround that? -- Michal Hocko SUSE Labs