Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp637460imm; Wed, 18 Jul 2018 08:11:06 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcL9jdI0P3YZfb6SDr9l8vaH079zlYdh/gHV9wh25Gr1Vr+/It/Kce6WQta5ggOSpy6c3xz X-Received: by 2002:a65:608b:: with SMTP id t11-v6mr6172206pgu.259.1531926666806; Wed, 18 Jul 2018 08:11:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531926666; cv=none; d=google.com; s=arc-20160816; b=q2Mi+RFDplDjpC4AcstVSsza9rsQOYf/bYqGEVgZknD5jzVS8IRhJlfpvsXWawJ/Yc L+DJkLBLCdM/PdXV54+e6V23dttMw029hVWlm07RV0fugKEE/OqqwXv0E3RoJwEuFPtk QJ84xP2/g1LLSYHFeDfYMQZcr16K/4lEjRwxeQG+4Mb4TBqSrXFSk4RLgXYW2KP0XqIc a3JOcUaljOXzYeJyfc+BEenVusC6ytdqb8vVSfGmCUf2gm3NYRC7er9SaVYQJCW9Ltfh HAhiVs5LkbQvOyH5f2hn4CmWs7N72s793KTNt6ppfoxhW2CetTZy45WmGrUto6qqF7mC gcNw== 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:arc-authentication-results; bh=Ze6d6k+3KMibtGDi1OHA3fT2duHIgsHdhg5zKctaxGY=; b=Z0RPXJOSpqPi3RVi3NthEIKtgcdjBErWGX7D3xzwH91FD6x576jqg4n52gWVnEMGHJ BR9xidRF5Kf9fwKMI0S4iiREhEHR/JICc9Oyr8/DNynHwrW8gyrVu3f3u+/HuTPvw8Xg Iucbnhn8EUA6lQ5IWjpyHBez9qqbrvGp/kcUsNfKxU1zRviz1eV7jOS1FeGpLEgYIOUr 6s4AurDn0VWTu/qPHzV8kV6cMgAiHIBN6BGFPsoeXuqBmvBJP/dQKIfraWe/D+B6FLe1 EwNosfBT6+jgF6WobNgnKI13dmLYAn8lMwB3CEiEeCLMIEEVf63AghYWez5beQwhnt3o 0UZQ== 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 6-v6si3335618plb.409.2018.07.18.08.10.51; Wed, 18 Jul 2018 08:11:06 -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 S1730543AbeGRPsc (ORCPT + 99 others); Wed, 18 Jul 2018 11:48:32 -0400 Received: from mx2.suse.de ([195.135.220.15]:56146 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729462AbeGRPsc (ORCPT ); Wed, 18 Jul 2018 11:48:32 -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 72FC0AED2; Wed, 18 Jul 2018 15:10:10 +0000 (UTC) Date: Wed, 18 Jul 2018 17:10:09 +0200 From: Michal Hocko To: David Rientjes Cc: Baoquan He , linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, corbet@lwn.net, linux-doc@vger.kernel.org Subject: Re: [PATCH] mm/page_alloc: Deprecate kernelcore=nn and movable_core= Message-ID: <20180718151009.GJ7193@dhcp22.suse.cz> References: <20180717131837.18411-1-bhe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 17-07-18 13:46:43, David Rientjes wrote: > On Tue, 17 Jul 2018, Baoquan He wrote: > > > We can still use 'kernelcore=mirror' or 'movable_node' for the usage > > of hotplug and movable zone. If somebody shows up with a valid usecase > > we can reconsider. > > > > We actively use kernelcore=n%, I had recently added support for the option > in the first place in 4.17. It's certainly not deprecated. > > commit a5c6d6509342785bef53bf9508e1842b303f1878 > Author: David Rientjes > Date: Thu Apr 5 16:23:09 2018 -0700 > > mm, page_alloc: extend kernelcore and movablecore for percent What kind of functionality do you need to not depend on this knob? I mean it is a gross hack and you are basically working around fragmentation issues. ZONE_MOVABLE doesn't seem to be a long term solution here IMHO. -- Michal Hocko SUSE Labs